@finalout
@node Top, Fixes and changes after 2.16.0, (dir), (dir)
-@top New features in 2.16
+@chapter New features in 2.16
@menu
* Fixes and changes after 2.16.0::
@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.}
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
@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
@end example
-@unnumberedsubsubsec Solaris
+@unnumberedsubsec Solaris
Solaris7, ./configure
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}.
@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
@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),
used by us. Hopefully this will change in the future.
-@subsubheading Version-specific texinfo macros
+@subheading Version-specific texinfo macros
@itemize
@node Top
@top
+@menu
+* Compile::
+@end menu
+
+
@contents
@include macros.itexi
+
+@node Compile
+@chapter Compile
+
@include included/compile.itexi
@bye
...
@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.
-@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.
-@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.
-@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}
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}.
-@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.
-@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.
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
+lilypond (2.16.2-2) unstable; urgency=low
+
+ * Fix bad syntax in texinfo documentation exposed by texinfo >= 5.1
+ (closes: #707190)
+
+ -- Don Armstrong <don@debian.org> Wed, 15 May 2013 11:40:14 -0700
+
lilypond (2.16.2-1) unstable; urgency=low
* Release 2.16.2-1 to unstable