Split WWW target in two stages WWW-1 and WWW-2

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

diff --git a/Documentation/user/install.itely b/Documentation/user/install.itely
index faad7342a372d47bc81b106844825ff78456e6e0..277aaa0e6d2b56e1b09051465ea8c50e23821b21 100644 (file)
--- a/Documentation/user/install.itely
+++ b/Documentation/user/install.itely
@@ -7,6 +7,8 @@
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
+@c \version "2.11.38"
+
 @ifclear INSTALL
 @node Install
 @chapter Install
@@ -110,7 +112,7 @@ For information on packaging, see @uref{http://lilypond.org/devel}.
 
 @unnumberedsubsubsec Compilation
 
-In addition to the packages needed for running Lilypond (see below), you
+In addition to the packages needed for running LilyPond (see below), you
 need the following extra packages for building.
 
 When installing a binary package FOO, you may need to install the
@@ -130,8 +132,8 @@ install guile-devel or guile-dev or libguile-dev too.
 
 @item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.11 or newer).
 
-@item @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 4.x or
-newer). 
+@item @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 3.4 or
+newer.  4.x is strongly recommended).
 
 @item @uref{http://www.python.org,Python} (version 2.4 or newer)
 
@@ -177,7 +179,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
+This process requires a successful compile of LilyPond, and some
 additional tools and packages
 
 @itemize
@@ -274,7 +276,7 @@ make conf=prof install
 @node Building documentation without compiling LilyPond
 @subsection Building documentation without compiling LilyPond
 
-The documentation can be built locally without compiling lilypond from
+The documentation can be built locally without compiling LilyPond from
 scratch.
 
 From a fresh git checkout, do
@@ -304,7 +306,7 @@ export LD_LIBRARY_PATH=/usr/lib
 exec /usr/bin/pngtopnm "$@"
 @end verbatim
 
-On OSX, I use this:
+On MacOS@tie{}X, I use this:
 
 @verbatim
 export DYLD_LIBRARY_PATH=/sw/lib
@@ -317,7 +319,7 @@ writing a script like this:
 
 @verbatim
 ### run from Documentation/user/
-#  possibly required on OSX and/or old texinfo
+#  possibly required on OS X and/or old texinfo
 # ulimit -n 4096
 if [ -e out-www/lilypond.texi ]; then rm out-www/lilypond.* ; fi;
 if [ -e out-www/lilypond-program.texi ]; then rm
@@ -437,7 +439,7 @@ for your hierarchy.)
 
 @unnumberedsubsubsec International fonts
 
-On MacOs X, all fonts are installed by default.  However, finding all
+On MacOS@tie{}X, all fonts are installed by default.  However, finding all
 system fonts requires a bit of configuration; see
 @uref{http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html,
 this post} on the @code{lilypond-user} mailing list.