\lilypond@{ YOUR LILYPOND CODE @}
@end example
+Additionally, @code{\lilypondversion} displays the current version
+of lilypond.
Running @command{lilypond-book} yields a file that can be further
-processed with @LaTeX{}.
+processed with @LaTeX{}.
We show some examples here. The @code{lilypond} environment
\begin@{lilypond@}...\end@{lilypond@}
@end example
+
@seealso
There are specific @command{lilypond-book} command line options and
other details to know when processing @LaTeX{} documents, see
@@lilypondfile[options,go,here]@{@var{filename}@}
@end example
+Additionally, @code{@@lilypondversion} displays the current version
+of lilypond.
+
When @command{lilypond-book} is run on it, this results in a Texinfo
file (with extension @file{.texi}) containing @code{@@image} tags for
HTML, Info and printed output. @command{lilypond-book} generates images
\key c \minor c4 es g2
</lilypond>
@end example
-
@noindent
@command{lilypond-book} then produces an HTML file with appropriate image
tags for the music fragments:
Some music in <lilypond relative=2: a b c/> a line of text.
@end example
+
To include separate files, say
@example
<lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
@end example
+Additionally, @code{<lilypondversion/>} displays the current version
+of lilypond.
+
+
@cindex titling in HTML
@cindex preview image
@cindex thumbnail
equal that of the line width, i.e., @code{ragged-right = ##f} is
added to the LilyPond snippet.
-@c does this option still exist in lilypond? -jm
-@item packed
-Produce lines with packed spacing, i.e., @code{packed = ##t} is added
-to the LilyPond snippet.
-
@item line-width
@itemx line-width=@var{size}\@var{unit}
Set line width to @var{size}, using @var{unit} as units. @var{unit} is
quotes), quoting the source in the verbatim block will start after the
last occurrence of such a comment; similarly, quoting the source verbatim
will stop just before the first occurrence of a comment containing
-@samp{end verbatim}, it there is any. In the following source file
+@samp{end verbatim}, if there is any. In the following source file
example, the music will be interpreted in relative mode, but the
verbatim quote will not show the @code{relative} block, i.e.
f2 e
@end example
+@noindent
+If you would like to translate comments and variable names in verbatim
+output but not in the sources, you may set the environment variable
+@code{LYDOC_LOCALEDIR} to a directory path; the directory should
+contain a tree of @file{.mo} message catalogs with @code{lilypond-doc}
+as a domain.
+
@item addversion
(Only for Texinfo output.) Prepend line @code{\version
@@w@{"@@version@{@}"@}} to @code{verbatim} output.
the following command line gives the expected result
@example
-lilypond-book --process="lilypond --format=tex --tex \
- --header=texidoc test.texinfo
+lilypond-book --pdf --process="lilypond \
+ -dbackend=eps --header=texidoc" test.texinfo
@end example
Most LilyPond test documents (in the @file{input} directory of the
The same remark about @code{texidoc} processing with localized
languages also applies to @code{doctitle}.
+@item nogettext
+(Only for Texinfo output.) Do not translate comments and variable
+names in the snippet quoted verbatim.
+
@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
extension @command{lilypond-book} uses for the output file, and if the
input file is in the same directory as @command{lilypond-book} working
directory, you must use @code{--output} option to make
-@command{lilypond-book} running, otherwise the will exit with an error
+@command{lilypond-book} running, otherwise it will exit with an error
message like @qq{Output would overwrite input file}.