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