1 @c -*- coding: latin-1; mode: texinfo; -*-
8 ** AARGH. We also have tutorial.itely: Integrating text and music.
10 Could also do with a cleanup. Lost inspiration to fix this manual
11 where to describe what?
16 @c Note: keep this node named so that `info lilypond-book' brings you here.
18 @chapter @command{lilypond-book}: Integrating text and music
20 If you want to add pictures of music to a document, you can simply do it
21 the way you would do with other types of pictures. The pictures are
22 created separately, yielding PostScript output or PNG images, and those
23 are included into a La@TeX{} or HTML document.
25 @command{lilypond-book} provides a way to automate this process: This
26 program extracts snippets of music from your document, runs
27 @command{lilypond} on them, and outputs the document with pictures
28 substituted for the music. The line width and font size definitions for
29 the music are adjusted to match the layout of your document.
31 This procedure may be applied to La@TeX{}, HTML or Texinfo documents.
34 * An example of a musicological document::
35 * Integrating LaTeX and music::
36 * Integrating Texinfo and music::
37 * Integrating HTML and music::
38 * Music fragment options::
39 * Invoking lilypond-book::
40 * Filename extensions::
44 @node An example of a musicological document
45 @section An example of a musicological document
48 @cindex La@TeX{}, music in
49 @cindex HTML, music in
50 @cindex Texinfo, music in
51 Some texts contain music examples. These texts are musicological
52 treatises, songbooks, or manuals like this. Such texts can be made by
53 hand, simply by importing a PostScript figure into the word processor.
54 However, there is an automated procedure to reduce the amount of work
55 involved in HTML, La@TeX{}, and Texinfo documents.
57 A script called @code{lilypond-book} will extract the music fragments,
58 format them, and put back the resulting notation. Here we show a small
59 example for use with La@TeX{}. The example also contains explanatory
60 text, so we will not comment on it further.
64 \documentclass[a4paper]{article}
67 Documents for @command{lilypond-book} may freely mix music and text.
72 c2 g'2 \times 2/3 { f8 e d } c'2 g4
76 Options are put in brackets.
78 \begin[fragment,quote,staffsize=26,verbatim]{lilypond}
82 Larger examples can be put into a separate file, and introduced with
85 \lilypondfile[quote,noindent]{screech-boink.ly}
91 Under Unix, you can view the results as follows
96 lilypond-book --output=out lilybook.tex
97 @emph{lilypond-book (GNU LilyPond) 2.5.0}
98 @emph{Reading lilybook.tex...}
99 @emph{..lots of stuff deleted..}
100 @emph{Compiling out/lilybook.tex...}
103 @emph{lots of stuff deleted}
107 To convert the file into a PDF document, run the following commands
110 dvips -Ppdf -u+lilypond -u+ec-mftrace lilybook
114 Running @command{lilypond-book} and @command{latex} creates a lot of
115 temporary files, which would clutter up the working directory. To
116 remedy this, use the @code{--output=@var{dir}} option. It will create
117 the files in a separate subdirectory @file{dir}.
119 Finally the result of the La@TeX{} example shown above.@footnote{This
120 tutorial is processed with Texinfo, so the example gives slightly
121 different results in layout.} This finishes the tutorial section.
125 Documents for @command{lilypond-book} may freely mix music and text.
130 c2 g'2 \times 2/3 { f8 e d } c'2 g4
134 Options are put in brackets.
136 @lilypond[fragment,quote,staffsize=26,verbatim]
140 Larger examples can be put into a separate file, and introduced with
141 @code{\lilypondfile}.
143 @lilypondfile[quote,noindent]{screech-boink.ly}
152 @cindex documents, adding music to
155 @node Integrating LaTeX and music
156 @section Integrating La@TeX{} and music
158 La@TeX{} is the de-facto standard for publishing layouts in the exact
159 sciences. It is built on top of the @TeX{} typesetting engine,
160 providing the best typography available anywhere.
163 @uref{http://@/www@/.ctan@/.org/@/tex@/-archive/@/info/@/lshort/@/english/,
164 @emph{The Not So Short Introduction to La@TeX{}}} for an overview on how
167 Music is entered using
170 \begin[options,go,here]@{lilypond@}
179 \lilypondfile[options,go,here]@{@var{filename}@}
186 \lilypond@{ YOUR LILYPOND CODE @}
189 Running @command{lilypond-book} yields a file that can be further
190 processed with La@TeX{}.
192 We show some examples here. The lilypond environment
195 \begin[quote,fragment,staffsize=26]@{lilypond@}
203 @lilypond[quote,fragment,staffsize=26]
210 \lilypond[quote,fragment,staffsize=11]@{<c' e' g'>@}
216 @lilypond[quote,fragment,staffsize=11]{<c' e' g'>}
219 Currently, you cannot include @code{@{} or @code{@}} within
220 @code{\lilypond@{@}}, so this command is only useful with the
221 @code{fragment} option.
223 The default linewidth of the music will be adjusted by examining the
224 commands in the document preamble, the part of the document before
225 @code{\begin@{document@}}. The @command{lilypond-book} command sends
226 these to La@TeX{} to find out how wide the text is. The line width for
227 the music fragments is then adjusted to the text width. Note that this
228 heuristic algorithm can fail easily; in such cases it is necessary to
229 use the @code{linewidth} music fragment option.
231 @cindex titling and lilypond-book
232 @cindex @code{\header} in La@TeX{} documents
234 Each snippet calls @code{\preLilyPondExample} before and
235 @code{\postLilyPondExample} after the music if those macros have been
238 @cindex Latex, feta symbols
241 To include feta symbols (such as flat, segno, etc) in a LaTeX
242 document, use @code{\input@{titledefs@}}
245 \documentclass[a4paper]@{article@}
256 The font symbol names are defined in the file feta20.tex; to find
257 the location of this file, use the command
263 @cindex outline fonts
266 @cindex invoking dvips
268 For printing the La@TeX{} document you need a DVI to PostScript
269 translator like @command{dvips}. To use @command{dvips} to produce
270 a PostScript file, add the following options to the @command{dvips}
274 -Ppdf -u+lilypond.map -u+ec-mftrace.map
278 PDF can then be produced with a PostScript to PDF translator like
279 @code{ps2pdf} (which is part of GhostScript).
281 @cindex international characters
285 @node Integrating Texinfo and music
286 @section Integrating Texinfo and music
288 Texinfo is the standard format for documentation of the GNU project. An
289 example of a Texinfo document is this manual. The HTML, PDF, and Info
290 versions of the manual are made from the Texinfo document.
292 In the input file, music is specified with
295 @@lilypond[options,go,here]
304 @@lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
311 @@lilypondfile[options,go,here]@{@var{filename}@}
314 When @command{lilypond-book} is run on it, this results in a Texinfo
315 file (with extension @file{.texi}) containing @code{@@image} tags for
316 HTML and info output. For the printed edition, the raw @TeX{} output of
317 LilyPond is included in the main document.
319 We show two simple examples here. A @code{lilypond} environment
337 @@lilypond[fragment,staffsize=11]@{<c' e' g'>@}
343 @lilypond[fragment,staffsize=11]{<c' e' g'>}
345 Contrary to La@TeX{}, @code{@@lilypond@{...@}} does not generate an
346 in-line image. It always gets a paragraph of its own.
348 When using the Texinfo output format, @command{lilypond-book} also
349 generates bitmaps of the music (in PNG format), so you can make an HTML
350 document with embedded music.
353 @node Integrating HTML and music
354 @section Integrating HTML and music
356 Music is entered using
359 <lilypond fragment relative=2>
360 \key c \minor c4 es g2
365 @command{lilypond-book} then produces an HTML file with appropriate image
366 tags for the music fragments:
368 @lilypond[fragment,relative=2]
369 \key c \minor c4 es g2
372 For inline pictures, use @code{<lilypond ... />}, where the options
373 are separated by a colon from the music, for example
376 Some music in <lilypond relative=2: a b c/> a line of text.
379 To include separate files, say
382 <lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
385 @cindex titling in HTML
386 @cindex preview image
390 @node Music fragment options
391 @section Music fragment options
393 In the following, a ``LilyPond command'' refers to any command described
394 in the previous sections which is handled by @command{lilypond-book} to
395 produce a music snippet. For simplicity, LilyPond commands are only
396 shown in La@TeX{} syntax.
398 Note that the option string is parsed from left to right; if an option
399 occurs multiple times, the last one is taken.
401 The following options are available for LilyPond commands:
404 @item staffsize=@var{ht}
405 Set staff size to @var{ht}, which is measured in points.
408 Produce ragged-right lines with natural spacing (i.e., @code{raggedright
409 = ##t} is added to the LilyPond snippet). This is the default for the
410 @code{\lilypond@{@}} command if no @code{linewidth} option is present.
411 It is also the default for the @code{lilypond} environment if the
412 @code{fragment} option is set, and no line width is explicitly
416 @itemx linewidth=@var{size}\@var{unit}
417 Set line width to @var{size}, using @var{unit} as units. @var{unit} is
418 one of the following strings: @code{cm}, @code{mm}, @code{in}, or
419 @code{pt}. This option affects LilyPond output (this is, the staff
420 length of the music snippet), not the text layout.
422 If used without an argument, set line width to a default value (as
423 computed with a heuristic algorithm).
425 If no @code{linewidth} option is given, @command{lilypond-book} tries to
426 guess a default for @code{lilypond} environments which don't use the
427 @code{raggedright} option.
430 Do not print the time signature.
433 Make @command{lilypond-book} add some boilerplate code so that you can
441 without @code{\layout}, @code{\score}, etc.
444 Don't add additional code to complete LilyPond code in music snippets.
445 Since this is the default, @code{nofragment} is redundant normally.
447 @item indent=@var{size}\@var{unit}
448 Set indentation of the first music system to @var{size}, using
449 @var{unit} as units. @var{unit} is one of the following strings:
450 @code{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
451 LilyPond, not the text layout.
454 Set indentation of the first music system to zero. This option affects
455 LilyPond, not the text layout. Since no indentation is the default,
456 @code{noindent} is redundant normally.
459 Reduce line length of a music snippet by @math{2*0.4}@dmn{in} and put
460 the output into a quotation block. The value `0.4@dmn{in}' can be
461 controlled with the @code{exampleindent} option.
464 Set the amount by which the @code{quote} option indents a music snippet.
467 @itemx relative=@var{n}
468 Use relative octave mode. By default, notes are specified relative to
469 middle@tie{}C. The optional integer argument specifies the octave of
470 the starting note, where the default @code{1} is middle C.
473 LilyPond also uses @command{lilypond-book} to produce its own
474 documentation. To do that, some more obscure music fragment options are
479 The argument of a LilyPond command is copied to the output file and
480 enclosed in a verbatim block, followed by any text given with the
481 @code{intertext} option (not implemented yet); then the actual music is
482 displayed. This option does not work well with @code{\lilypond@{@}} if
483 it is part of a paragraph.
486 (Only for Texinfo output.) If @command{lilypond} is called with the
487 @option{--header=@/texidoc} option, and the file to be processed is
488 called @file{foo@/.ly}, it creates a file @file{foo@/.texidoc} if there
489 is a @code{texidoc} field in the @code{\header}. The @code{texidoc}
490 option makes @command{lilypond-book} include such files, adding its
491 contents as a documentation block right before the music snippet.
493 Assuming the file @file{foo@/.ly} contains
497 texidoc = "This file demonstrates a single note."
503 and we have this in our Texinfo document @file{test.texinfo}
506 @@lilypondfile[texidoc]@{foo.ly@}
510 the following command line gives the expected result
513 lilypond-book --process="lilypond --format=tex --tex \
514 --header=texidoc test.texinfo
517 Most LilyPond test documents (in the @file{input} directory of the
518 distribution) are small @file{.ly} files which look exactly like this.
521 If a LilyPond input file is included with @code{\lilypondfile}, print
522 the file name right before the music snippet. For HTML output, this is
526 This option includes fonts in all of the generated EPS-files for this
527 snippet. This should be used if the snippet uses any font that LaTeX
528 cannot find on its own.
533 @node Invoking lilypond-book
534 @section Invoking @command{lilypond-book}
536 @command{lilypond-book} produces a file with one of the following
537 extensions: @file{.tex}, @file{.texi}, or @file{.html}, depending on the
538 output format. Both @file{.tex} and @file{.texi} files need further
541 To produce PDF output from the @file{.tex} file, you should do
545 dvips -Ppdf -u+ec-mftrace.map -u+lilypond.map yourfile.dvi
549 To produce a Texinfo document (in any output format), follow the normal
550 procedures for Texinfo (this is, either call @command{texi2dvi} or
551 @command{makeinfo}, depending on the output format you want to create).
552 @xref{Format with texi2dvi, , , texinfo, GNU Texinfo}, and @ref{Creating
553 an Info File, , , texinfo, GNU Texinfo}.
555 @command{lilypond-book} accepts the following command line options:
558 @item -f @var{format}
559 @itemx --format=@var{format}
560 Specify the document type to process: @code{html}, @code{latex}, or
561 @code{texi} (the default). If this option is missing,
562 @command{lilypond-book} tries to detect the format automatically.
564 The @code{texi} document type produces a Texinfo file with music
565 fragments in the DVI output only. For getting images in the HTML
566 version, the format @code{texi-html} must be used instead.
568 [Note: Currently, @code{texi} is the same as @code{texi-html}.]
570 @item -F @var{filter}
571 @itemx --filter=@var{filter}
572 Pipe snippets through @var{filter}.
576 lilypond-book --filter='convert-ly --from=2.0.0' my-book.tely
581 Print a short help message.
584 @itemx --include=@var{dir}
585 Add @var{dir} to the include path.
588 @itemx --output=@var{dir}
589 Place generated files in directory @var{dir}. Running
590 @command{lilypond-book} generates lots of small files that LilyPond will
591 process. To avoid all that garbage in the source directory use the
592 @option{--output} command line option, and change to that directory
593 before running @command{latex} or @command{makeinfo}:
596 lilypond-book --output=out yourfile.lytex
601 @item -P @var{process}
602 @itemx --process=@var{command}
603 Process LilyPond snippets using @var{command}. The default command is
612 Print version information.
617 The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
618 La@TeX{} commands that change margins and line widths after the preamble
621 Only the first @code{\score} of a LilyPond block is processed.
624 The size of a music block is limited to 1.5 KB, due to technical
625 problems with the Python regular expression engine. For longer files,
626 use @code{\lilypondfile}.
629 @node Filename extensions
630 @section Filename extensions
632 You can use any filename extension for the input file, but if you do not
633 use the recommended extension for a particular format you may need to
634 manually specify the output format. @xref{Invoking lilypond-book}, for
635 details. Otherwise, @command{lilypond-book} automatically selects the
636 output format based on the input filename's extension.
639 @multitable @columnfractions .2 .5
640 @item @strong{extension} @tab @strong{output format}
642 @item @file{.html} @tab HTML
643 @item @file{.itely} @tab Texinfo
644 @item @file{.latex} @tab La@TeX{}
645 @item @file{.lytex} @tab La@TeX{}
646 @item @file{.tely} @tab Texinfo
647 @item @file{.tex} @tab La@TeX{}
648 @item @file{.texi} @tab Texinfo
649 @item @file{.texinfo} @tab Texinfo
650 @item @file{.xml} @tab HTML