Running @command{lilypond-book} and @command{latex} creates a lot of
temporary files, which would clutter up the working directory. To
-remedy this, use the @code{--output=@var{dir}} option. It will create
+remedy this, use the @option{--output=@var{dir}} option. It will create
the files in a separate subdirectory @file{dir}.
Finally the result of the @LaTeX{} example shown above.@footnote{This
@emph{The Not So Short Introduction to @LaTeX{}}} for an overview on how
to use @LaTeX{}.
-Music is entered using
+@code{lilypond-book} provides the following commands and environments to include
+music in @LaTeX{} files:
+
+@itemize @bullet
+@item the @code{\lilypond@{...@}} command, where you can directly enter short lilypond code
+@item the @code{\begin@{lilypond@}...\end@{lilypond@}} environment, where you can directly enter longer lilypond code
+@item the @code{\lilypondfile@{...@}} command to insert a lilypond file
+@item the @code{\musicxmlfile@{...@}} command to insert a MusicXML file, which will be processed by @code{musicxml2ly} and @code{lilypond}.
+@end itemize
+
+In the input file, music is specified with
@example
\begin@{lilypond@}[options,go,here]
or
@example
-\lilypondfile[options,go,here]@{@var{filename}@}
+\lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
@end example
+or
-@noindent
+@example
+\lilypondfile[options,go,here]@{@var{filename}@}
+@end example
or
@example
-\lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
+\musicxmlfile[options,go,here]@{@var{filename}@}
@end example
+
+@noindent
+
Additionally, @code{\lilypondversion} displays the current version
of lilypond.
Running @command{lilypond-book} yields a file that can be further
example of a Texinfo document is this manual. The HTML, PDF, and Info
versions of the manual are made from the Texinfo document.
+@code{lilypond-book} provides the following commands and environments to include
+music into Texinfo files:
+
+@itemize @bullet
+@item the @code{@@lilypond@{...@}} command, where you can directly enter short lilypond code
+@item the @code{@@lilypond...@@end lilypond} environment, where you can directly enter longer lilypond code
+@item the @code{@@lilypondfile@{...@}} command to insert a lilypond file
+@item the @code{@@musicxmlfile@{...@}} command to insert a MusicXML file, which will be processed by @code{musicxml2ly} and @code{lilypond}.
+@end itemize
+
In the input file, music is specified with
@example
@example
@@lilypondfile[options,go,here]@{@var{filename}@}
@end example
+or
+
+@example
+@@musicxmlfile[options,go,here]@{@var{filename}@}
+@end example
Additionally, @code{@@lilypondversion} displays the current version
of lilypond.
@node HTML
@subsection HTML
+@code{lilypond-book} provides the following commands and environments to include
+music in HTML files:
+
+@itemize @bullet
+@item the @code{<lilypond .... />} command, where you can directly enter short lilypond code
+@item the @code{<lilyond>...</lilypond>} environment, where you can directly enter longer lilypond code
+@item the @code{<lilypondfile>...</lilypondfile>} command to insert a lilypond file
+@item the @code{<musicxmlfile>...</musicxmlfile>} command to insert a MusicXML file, which will be processed by @code{musicxml2ly} and @code{lilypond}.
+@end itemize
+
Music is entered using
@example
<lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
@end example
+@code{<musicxmlfile>} uses the same syntax as @code{<lilypondfile>}, but simply
+references a MusicXML file rather than a LilyPond file.
+
For a list of options to use with the @code{lilypond} or
@code{lilypondfile} tags, see @ref{Music fragment options}.
Running @command{dvips} may produce some warnings about fonts; these
are harmless and may be ignored. If you are running @command{latex} in
-twocolumn mode, remember to add @code{-t landscape} to the
+twocolumn mode, remember to add @option{-t landscape} to the
@command{dvips} options.
@subsubheading Texinfo
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.
+@command{latex} with the same @option{-I @var{dir}} options.
@item -o @var{dir}
@itemx --output=@var{dir}
LilyPond Info documentation without images.
@itemx --lily-output-dir=@var{dir}
-Write lily-XXX files to directory @var{dir}, link into @code{--output}
+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.
@item -P @var{command}
@itemx --process=@var{command}
Process LilyPond snippets using @var{command}. The default command is
-@code{lilypond}. @code{lilypond-book} will not @code{--filter} and
-@code{--process} at the same time.
+@code{lilypond}. @code{lilypond-book} will not @option{--filter} and
+@option{--process} at the same time.
@item --pdf
Create PDF files for use with PDF@LaTeX{}.
@itemx --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 @code{--output-dir} and
-@code{--lily-output-dir} options are different.
+and only if directories implied by @option{--output-dir} and
+@option{--lily-output-dir} options are different.
@item -V
@itemx --verbose
If you use the same filename extension for the input file than the
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
+directory, you must use @option{--output} option to make
@command{lilypond-book} running, otherwise it will exit with an error
message like @qq{Output would overwrite input file}.