Save the code above to a file called @file{lilybook.lytex}, then in a
terminal run
+@c keep space after @version{} so TeX doesn't choke
@example
lilypond-book --output=out --pdf lilybook.lytex
-@emph{lilypond-book (GNU LilyPond) 2.11.37}
+@emph{lilypond-book (GNU LilyPond) @version{} }
@emph{Reading lilybook.lytex...}
@emph{..lots of stuff deleted..}
@emph{Compiling lilybook.tex...}
@end ignore
-@commonprop
+@snippets
Sometimes it is useful to display music elements (such as ties and slurs)
as if they continued after the end of the fragment. This can be done by
f2 e
@end example
+@item addversion
+(Only for Texinfo output.) Prepend line @code{\version
+@@w{"@@version@{@}"}} to @code{verbatim} output.
+
@item texidoc
(Only for Texinfo output.) If @command{lilypond} is called with the
@option{--header=@/texidoc} option, and the file to be processed is
@item printfilename
If a LilyPond input file is included with @code{\lilypondfile}, print
-the file name right before the music snippet. For HTML output, this is
-a link.
+the file name right before the music snippet. For HTML output, this
+is a link. Only the base name of the file is printed, i.e. the
+directory part of the file path is stripped.
@item fontload
This option includes fonts in all of the generated EPS-files for this
@noindent
The @file{.dvi} file created by this process will not contain
-noteheads. This is normal; if you follow the instructions, they
+ note heads. This is normal; if you follow the instructions, they
will be included in the @file{.ps} and @file{.pdf} files.
Running @command{dvips} will produce some warnings about fonts; these
Specify the document type to process: @code{html}, @code{latex},
@code{texi} (the default) or @code{docbook}. If this option is missing,
@command{lilypond-book} tries to detect the format automatically, see
-@ref{Filename extensions}.
+@ref{Filename extensions}. Currently, @code{texi} is the same as
+@code{texi-html}.
@c This complicated detail is not implemented, comment it out -jm
@ignore
The @code{texi} document type produces a Texinfo file with music
fragments in the printed output only. For getting images in the HTML
version, the format @code{texi-html} must be used instead.
-
-[Note: currently, @code{texi} is the same as @code{texi-html}.]
@end ignore
@item -F @var{filter}
@item -I @var{dir}
@itemx --include=@var{dir}
-Add @var{dir} to the include path.
+Add @var{dir} to the include path. @command{lilypond-book} also looks
+for already compiled snippets in the include path, and does not write
+them back to the output directory, so in some cases it is necessary to
+invoke further processing commands such as @command{makeinfo} or
+@command{latex} with the same @code{-I @var{dir}} options.
@item -o @var{dir}
@itemx --output=@var{dir}
@code{lilypond}. @code{lilypond-book} will not @code{--filter} and
@code{--process} at the same time.
+@item --pdf
+Create PDF files for use with PDFLaTeX.
+
@itemx --psfonts
Extract all PostScript fonts into @file{@var{file}.psfonts} for dvips.
This is necessary for @command{dvips -h @var{file}.psfonts}.
Print version information.
@end table
-@refbugs
+@knownissues
The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
@LaTeX{} commands that change margins and line widths after the preamble