Merge master into nested-bookparts

[lilypond.git] / Documentation / user / install.itely

diff --git a/Documentation/user/install.itely b/Documentation/user/install.itely
index e63cd63c224f894f66208df11bd8588ed78cd726..e203291674081bfc183cb2239b5b3810c238eab4 100644 (file)
--- a/Documentation/user/install.itely
+++ b/Documentation/user/install.itely
@@ -7,20 +7,13 @@
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
-@c \version "2.11.51"
+@c \version "2.11.61"
 
 @ifclear INSTALL
 @node Install
 @chapter Install
 @end ifclear
 
-@c  I don't know what this comment does.  Remove?  -gp
-@ignore
-@h tml
-<a name="download-source">
-@e nd html
-@end ignore
-
 There are two sets of releases for LilyPond: stable releases, and
 unstable development releases.  Stable versions have an even-numbered
 @q{minor} version number (i.e. 2.8, 2.10, 2.12, etc).  Development
@@ -39,7 +32,7 @@ recommend using the precompiled binaries.
 @node Precompiled binaries
 @section Precompiled binaries
 
-@subsection Downloading
+@unnumberedsubsec Downloading
 
 Check out @uref{http://lilypond.org/web/install/} for up to date
 information on binary packages for your platform.  If your operating
@@ -54,22 +47,43 @@ darwin-x86  - MacOS X intel
 freebsd-64  - FreeBSD 6.x, x86_64
 freebsd-x86 - FreeBSD 4.x, x86
 linux-64    - Any GNU/Linux distribution, x86_64
-linux-arm   - Any GNU/Linux distribution, arm
 linux-ppc   - Any GNU/Linux distribution, powerpc
 linux-x86   - Any GNU/Linux distribution, x86
 mingw       - Windows x86
 @end example
 
+@knownissues
+
+If you have MacOS 10.3 or 10.4 and you would like to use Python
+scripts such as @command{convert-ly} and @command{lilypond-book}, see
+@ref{Setup for MacOS X,,,lilypond-program,Application Usage}.
+
+
+@node Compiling from source
+@section Compiling from source
+
+@ignore
+You can also compile LilyPond directly from the source code. This
+requires that you can read English, so this section is not
+translated.  If you really want to compile LilyPond, see
+@iftex
+@c DO NOT translate the following line at all.
+@ref{Compiling from source,,,lilypond-program,Application Usage}.
+@end iftex
+@ifhtml
+@c Please translate the following line (but not the .html file name)
+the @uref{Compiling-from-source.html,documentation in English}.
+@end ifhtml
+@end ignore
 
 @c TRANSLATORS:
 @c   Please **do not** translate anything below this line.  Users
-@c   should not be compiling LilyPond themselves; if they really 
+@c   should not be compiling LilyPond themselves; if they really
 @c   want to do so, they should be able to read the English docs,
 @c   because they'll probably need to ask questions in English
 @c   on the -devel list.   -gp
-
-@node Compiling from source
-@section Compiling from source
+@c Instead, please uncomment and translate the paragraph above,
+@c and remove all stuff (menu, nodes, contents) below this line.
 
 @menu
 * Downloading source code::     
@@ -122,6 +136,11 @@ FOO-devel, libFOO-dev or FOO-dev package too.
 
 @item @uref{http://fontforge.sf.net/,FontForge} 20060125 or newer.
 
+@item @uref{http://metafont.tutorial.free.fr/,MetaFont} (mf-nowin, mf, mfw or 
+mfont binaries) and @uref{http://cm.bell-labs.com/who/hobby/MetaPost.html,MetaPost}
+(mpost binary), usually packaged with a @LaTeX{} distribution like
+tetex or texlive.
+
 @item @uref{http://www.lcdf.org/~eddietwo/type/#t1utils,t1utils}
 (version 1.33 or newer recommended).
 
@@ -183,7 +202,7 @@ or lyrics.
 You can view the documentation online at
 @uref{http://lilypond.org/doc/}, but you can also build it locally.
 This process requires a successful compile of LilyPond, and some
-additional tools and packages
+additional tools and packages:
 
 @itemize
 @item The @uref{http://netpbm.sourceforge.net/,netpbm utilities}
@@ -196,6 +215,10 @@ and the patch from
 @uref{http://bugs.ghostscript.com/show_bug.cgi?id=688017}, or use
 a release of Ghostscript which includes these patches, for example
 8.60 or newer.
+@item @uref{http://www.nongnu.org/texi2html/,Texi2HTML} 1.79 or newer
+is strongly recommended to build documentation in HTML; support for
+building HTML documentation using @command{makeinfo} from GNU Texinfo
+is deprecated.
 @end itemize
 
 
@@ -258,6 +281,14 @@ mkdir lily-build && cd lily-build
 
 @end example
 
+
+@unnumberedsubsubsec Useful @command{make} variables
+
+If a less verbose build output if desired, the variable
+@code{QUIET_BUILD} may be set to @code{1} on @command{make} command
+line, or in @file{local.make} at top of the build tree.
+
+
 @node Building documentation
 @subsection Building documentation
 
@@ -323,6 +354,9 @@ documentation maintenance are available from @file{Documentation/};
 for more information, see @file{Documentation/user/README.txt} and
 @file{Documentation/TRANSLATION}.
 
+The makefile variable @code{QUIET_BUILD} may be set to @code{1} for a
+less verbose build output, just like for building the programs.
+
 @knownissues
 
 @code{-j} command-line option of @command{make} is unsupported for
@@ -330,7 +364,7 @@ building the documentation.  As the most time consuming task is
 running LilyPond to build images of music, the makefile variable
 @code{CPU_COUNT} may be set in @file{local.make} or on the command line
 to the number of @code{.ly} files that LilyPond should process
-simultaneously, e.g. on a bi-processor or Dual core machine
+simultaneously, e.g. on a bi-processor or dual core machine
 
 @example
 make CPU_COUNT=2 web