1 \input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: nl -*-
2 @c This file is part of application.tely
4 Translation of GIT committish: 1b3da70d81938d19a2b107382bbe25a267cf130b
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. See TRANSLATION for details.
11 @c -*- coding: utf-8; mode: texinfo; -*-
13 @c Note: keep this node named so that `info lilypond-book' brings you here.
15 @chapter Running @command{lilypond-book}
20 @c ommand{lilypond-book} provides a way to automate this process: This
21 @c ommand{lilypond} on them, and outputs the document with pictures
22 @c ode{lilypond-book}, see FIXME FIXME @c @ref{Setup for MacOS X}.
29 @c index documents, adding music to
30 @c index HTML, music in
31 @c index Texinfo, music in
32 @c index DocBook, music in
33 @c index @LaTeX{}, music in
35 * An example of a musicological document::
36 * Integrating music and text::
37 * Music fragment options::
38 * Invoking lilypond-book::
39 * Filename extensions::
40 * Alternate methods of mixing text and music::
43 @node An example of a musicological document
44 @section An example of a musicological document
53 @subheading Processing
54 @c keep space after @version{} so TeX doesn't choke
56 @c ode{\lilypondfile}.
57 @node Integrating music and text
58 @section Integrating music and text
76 @c ode{\lilypond@{@}}, so this command is only useful with the
77 @c ode{fragment} option.
78 @c ode{\begin@{document@}}. The @command{lilypond-book} command sends
79 @c index titling and lilypond-book
80 @c index \header in @LaTeX{} documents
81 @c ode{lilypond-book} has split the snippet into several PostScript
82 @c index Latex, feta symbols
84 @ref{Invoking lilypond-book}.
97 @c ommand{lilypond-book} then produces an HTML file with appropriate image
98 @c index titling in HTML
99 @c index preview image
107 @subheading Common conventions
108 @c ode{inlinemediaobject} element, so our snippets can be formatted
109 @c ommand{lilypond-book} should have the extension @file{.lyxml}.
110 @subheading Including a LilyPond file
111 @subheading Including LilyPond code
112 @c ode{inlinemediaobject}, and there is a @code{textobject} containing
113 @subheading Processing the DocBook document
114 @node Music fragment options
115 @section Music fragment options
120 @c ode{ragged-right = ##t} is added to the LilyPond snippet. This is the
121 @c ode{pt}. This option affects LilyPond output (this is, the staff
122 @c ode{ragged-right} option.
123 @c ode{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
124 @c ode{noindent} is redundant normally.
125 @c ode{relative} option only works when @code{fragment} option is set,
126 @c ode{intertext} option (not implemented yet); then the actual music is
127 @c ode{LYDOC_LOCALEDIR} to a directory path; the directory should
128 @c ode{@@documentlanguage @var{LANG}} and @file{foo@/.ly} header
129 @c ode{verbatim} option) is put into a quotation block. This option is
130 @c ode{texidoc} documentation block.
131 @c ode{texidoc} option: if @command{lilypond} is called with the
132 @c ode{\header}, it creates a file @file{foo@/.doctitle}. When
133 @c ode{doctitle} option is used, the contents of @file{foo@/.doctitle},
134 @c ode{@@lydoctitle} should be a macro defined in the Texinfo document.
135 @node Invoking lilypond-book
136 @section Invoking @command{lilypond-book}
141 @c ommand{lilypond-book} produces a file with one of the following
142 @subheading Format-specific instructions
143 @subsubheading @LaTeX{}
144 @c ommand{dvips}. The first way is simpler and recommended@footnote{Note
145 @c index outline fonts
148 @c index invoking dvips
149 @c ommand{dvips} options.
150 @subsubheading Texinfo
151 @c ommand{texi2dvi} or @command{makeinfo}, depending on the output format
152 @subheading Command line options
153 @c ommand{lilypond-book} accepts the following command line options:
154 @c ode{texi} (the default) or @code{docbook}. If this option is missing,
155 @c ommand{lilypond-book} tries to detect the format automatically, see
156 @ref{Filename extensions}. Currently, @code{texi} is the same as
158 @c This complicated detail is not implemented, comment it out -jm
159 @c ommand{latex} with the same @code{-I @var{dir}} options.
160 @c ommand{lilypond-book} generates lots of small files that LilyPond will
161 @c ode{lilypond}. @code{lilypond-book} will not @code{--filter} and
162 @c ode{--process} at the same time.
163 @node Filename extensions
164 @section Filename extensions
171 @c ommand{lilypond-book} running, otherwise it will exit with an error
172 @node Alternate methods of mixing text and music
173 @section Alternative methods of mixing text and music
179 * Many quotes from a large score::
180 * Inserting LilyPond output into OpenOffice.org::
181 * Inserting LilyPond output into other programs::
184 @node Many quotes from a large score
185 @unnumberedsubsec Many quotes from a large score
190 @node Inserting LilyPond output into OpenOffice.org
191 @unnumberedsubsec Inserting LilyPond output into OpenOffice.org
196 @c index OpenOffice.org
197 @node Inserting LilyPond output into other programs
198 @unnumberedsubsec Inserting LilyPond output into other programs
204 @c -- SKELETON FILE --