Documentation fix for compatibility with texinfo 5.1

Patch by Don Armstrong (minus the @top change in changes.tely)

Fixes issue 3382.
http://code.google.com/p/lilypond/issues/detail?id=3382

diff --git a/Documentation/contributor/quick-start.itexi b/Documentation/contributor/quick-start.itexi
index 4788379f4ce1b1c56a94d2e1c98da385dd418173..7fab3911fd731133e655cb6ffd57be040f1030b7 100644 (file)
--- a/Documentation/contributor/quick-start.itexi
+++ b/Documentation/contributor/quick-start.itexi
@@ -344,7 +344,7 @@ to @ref{Compiling with LilyDev} before reading on.
 @warning{Throughout the rest of this manual, most command-line
 input should be entered from @file{~/lilypond-git/}.  This is
 known as the @emph{top source directory} and is often referred to as
 @warning{Throughout the rest of this manual, most command-line
 input should be entered from @file{~/lilypond-git/}.  This is
 known as the @emph{top source directory} and is often referred to as

-@var{$LILYPOND_GIT}}.
+@var{$LILYPOND_GIT}.}

 
 @warning{Only work on one set of changes at once.  Do not start
 work on any new changes until your first set has been accepted.}
 
 @warning{Only work on one set of changes at once.  Do not start
 work on any new changes until your first set has been accepted.}

diff --git a/Documentation/included/compile.itexi b/Documentation/included/compile.itexi
index 94513ea93612eec0d13284ac6ceac53996d035e2..cc2894019faf699194c5499614f71d772a22fb6b 100644 (file)
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -922,7 +922,7 @@ bug reports to @email{bug-lilypond@@gnu.org}.
 
 Bugs that are not fault of LilyPond are documented here.
 
 
 Bugs that are not fault of LilyPond are documented here.
 

-@unnumberedsubsubsec Bison 1.875
+@unnumberedsubsec Bison 1.875

 
 There is a bug in bison-1.875: compilation fails with "parse error
 before `goto'" in line 4922 due to a bug in bison.  To fix, please
 
 There is a bug in bison-1.875: compilation fails with "parse error
 before `goto'" in line 4922 due to a bug in bison.  To fix, please


@@ -937,7 +937,7 @@ $ make
 @end example
 
 
 @end example
 
 

-@unnumberedsubsubsec Compiling on MacOS@tie{}X
+@unnumberedsubsec Compiling on MacOS@tie{}X

 
 Here are special instructions for compiling under MacOS@tie{}X.
 These instructions assume that dependencies are installed using
 
 Here are special instructions for compiling under MacOS@tie{}X.
 These instructions assume that dependencies are installed using


@@ -989,7 +989,7 @@ automatic font detection, add
 @end example
 
 
 @end example
 
 

-@unnumberedsubsubsec Solaris
+@unnumberedsubsec Solaris

 
 Solaris7, ./configure
 
 
 Solaris7, ./configure
 


@@ -1008,7 +1008,7 @@ or
 CONFIG_SHELL=/bin/bash bash -c ./configure
 @end example
 
 CONFIG_SHELL=/bin/bash bash -c ./configure
 @end example
 

-@unnumberedsubsubsec FreeBSD
+@unnumberedsubsec FreeBSD

 
 To use system fonts, dejaview must be installed.  With the default
 port, the fonts are installed in @file{usr/X11R6/lib/X11/fonts/dejavu}.
 
 To use system fonts, dejaview must be installed.  With the default
 port, the fonts are installed in @file{usr/X11R6/lib/X11/fonts/dejavu}.


@@ -1022,7 +1022,7 @@ for your hierarchy.)
 @end example
 
 
 @end example
 
 

-@unnumberedsubsubsec International fonts
+@unnumberedsubsec International fonts

 
 On Mac OS X, all fonts are installed by default.  However, finding all
 system fonts requires a bit of configuration; see
 
 On Mac OS X, all fonts are installed by default.  However, finding all
 system fonts requires a bit of configuration; see


@@ -1049,7 +1049,7 @@ Debian GNU/Linux
 @end verbatim
 
 
 @end verbatim
 
 

-@unnumberedsubsubsec Using lilypond python libraries
+@unnumberedsubsec Using lilypond python libraries

 
 If you want to use lilypond's python libraries (either running
 certain build scripts manually, or using them in other programs),
 
 If you want to use lilypond's python libraries (either running
 certain build scripts manually, or using them in other programs),


@@ -1123,7 +1123,7 @@ We currently use make and stepmake, which is complicated and only
 used by us.  Hopefully this will change in the future.
 
 
 used by us.  Hopefully this will change in the future.
 
 

-@subsubheading Version-specific texinfo macros
+@subheading Version-specific texinfo macros

 
 @itemize
 
 
 @itemize
 

diff --git a/Documentation/topdocs/INSTALL.texi b/Documentation/topdocs/INSTALL.texi
index 47f0a7070361123d6db15700fcef074960b3b2c8..b562cc4d687f66b241d414be82bc3ffb5b7a722a 100644 (file)
--- a/Documentation/topdocs/INSTALL.texi
+++ b/Documentation/topdocs/INSTALL.texi
@@ -10,9 +10,18 @@
 @node Top
 @top
 
 @node Top
 @top
 

+@menu
+* Compilation::
+@end menu
+
+

 @contents
 
 @include macros.itexi
 @contents
 
 @include macros.itexi

+
+@node Compilation
+@chapter Compilation
+

 @include included/compile.itexi
 
 @bye
 @include included/compile.itexi
 
 @bye

diff --git a/Documentation/usage/lilypond-book.itely b/Documentation/usage/lilypond-book.itely
index 65c5823d08e0bbd4eff38e18d9dffd76ef95b29e..c14c49b43b3bcfd5f9c76715e82fa90b7a08c864 100644 (file)
--- a/Documentation/usage/lilypond-book.itely
+++ b/Documentation/usage/lilypond-book.itely
@@ -1003,20 +1003,20 @@ cd out
 @dots{}
 @end example
 
 @dots{}
 @end example
 

-@itemx --skip-lily-check
+@item --skip-lily-check

 Do not fail if no lilypond output is found.  It is used for LilyPond
 Info documentation without images.
 
 Do not fail if no lilypond output is found.  It is used for LilyPond
 Info documentation without images.
 

-@itemx --skip-png-check
+@item --skip-png-check

 Do not fail if no PNG images are found for EPS files.  It is used for
 LilyPond Info documentation without images.
 
 Do not fail if no PNG images are found for EPS files.  It is used for
 LilyPond Info documentation without images.
 

-@itemx --lily-output-dir=@var{dir}
+@item --lily-output-dir=@var{dir}

 Write lily-XXX files to directory @var{dir}, link into @option{--output}
 directory.  Use this option to save building time for documents in
 different directories which share a lot of identical snippets.
 
 Write lily-XXX files to directory @var{dir}, link into @option{--output}
 directory.  Use this option to save building time for documents in
 different directories which share a lot of identical snippets.
 

-@itemx --lily-loglevel=@var{loglevel}
+@item --lily-loglevel=@var{loglevel}

 Set the output verbosity of the invoked @command{lilypond} calls to
 @var{loglevel}.  Possible values are @code{NONE}, @code{ERROR},
 @code{WARNING}, @code{BASIC_PROGRESS}, @code{PROGRESS}, @code{INFO}
 Set the output verbosity of the invoked @command{lilypond} calls to
 @var{loglevel}.  Possible values are @code{NONE}, @code{ERROR},
 @code{WARNING}, @code{BASIC_PROGRESS}, @code{PROGRESS}, @code{INFO}


@@ -1025,16 +1025,16 @@ environment variable @code{LILYPOND_LOGLEVEL} is set, its value is used
 as the loglevel.
 
 
 as the loglevel.
 
 

-@itemx --info-images-dir=@var{dir}
+@item --info-images-dir=@var{dir}

 Format Texinfo output so that Info will look for images of music in
 @var{dir}.
 
 Format Texinfo output so that Info will look for images of music in
 @var{dir}.
 

-@itemx --latex-program=@var{prog}
+@item --latex-program=@var{prog}

 Run executable @command{prog} instead of @command{latex}.  This is
 useful if your document is processed with @command{xelatex}, for
 example.
 
 Run executable @command{prog} instead of @command{latex}.  This is
 useful if your document is processed with @command{xelatex}, for
 example.
 

-@itemx --left-padding=@var{amount}
+@item --left-padding=@var{amount}

 Pad EPS boxes by this much.  @var{amount} is measured in millimeters,
 and is 3.0 by default.  This option should be used if the lines of
 music stick out of the right margin.
 Pad EPS boxes by this much.  @var{amount} is measured in millimeters,
 and is 3.0 by default.  This option should be used if the lines of
 music stick out of the right margin.


@@ -1057,7 +1057,7 @@ Create PDF files for use with PDF@LaTeX{}.
 By default, output is displayed on the terminal.  This option redirects
 all output to log files in the same directory as the source files.
 
 By default, output is displayed on the terminal.  This option redirects
 all output to log files in the same directory as the source files.
 

-@itemx --use-source-file-names
+@item --use-source-file-names

 Write snippet output files with the same base name as their source file.
 This option works only for snippets included with @code{lilypondfile}
 and only if directories implied by @option{--output-dir} and
 Write snippet output files with the same base name as their source file.
 This option works only for snippets included with @code{lilypondfile}
 and only if directories implied by @option{--output-dir} and