1 @c -*- coding: utf-8; mode: texinfo; -*-
2 @c This file is part of lilypond-program.tely
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. See TRANSLATION for details.
12 @c Note: keep this node named so that `info lilypond-book' brings you here.
14 @chapter @command{lilypond-book}: Integrating text and music
16 If you want to add pictures of music to a document, you can simply do it
17 the way you would do with other types of pictures. The pictures are
18 created separately, yielding PostScript output or PNG images, and those
19 are included into a @LaTeX{} or HTML document.
21 @command{lilypond-book} provides a way to automate this process: This
22 program extracts snippets of music from your document, runs
23 @command{lilypond} on them, and outputs the document with pictures
24 substituted for the music. The line width and font size definitions for
25 the music are adjusted to match the layout of your document.
27 This is a separate program from @command{lilypond} itself, and is run on
28 the command-line; for more information, see @ref{Command-line usage}.
30 This procedure may be applied to @LaTeX{}, HTML, Texinfo or DocBook documents.
38 @cindex documents, adding music to
39 @cindex HTML, music in
40 @cindex Texinfo, music in
41 @cindex DocBook, music in
42 @cindex @LaTeX{}, music in
45 * An example of a musicological document::
46 * Integrating music and text::
47 * Music fragment options::
48 * Invoking lilypond-book::
49 * Filename extensions::
50 * Alternate methods of mixing text and music::
54 @node An example of a musicological document
55 @section An example of a musicological document
58 Some texts contain music examples. These texts are musicological
59 treatises, songbooks, or manuals like this. Such texts can be made by
60 hand, simply by importing a PostScript figure into the word processor.
61 However, there is an automated procedure to reduce the amount of work
62 involved in HTML, @LaTeX{}, Texinfo and DocBook documents.
64 A script called @code{lilypond-book} will extract the music fragments,
65 format them, and put back the resulting notation. Here we show a small
66 example for use with @LaTeX{}. The example also contains explanatory
67 text, so we will not comment on it further.
73 \documentclass[a4paper]{article}
77 Documents for \verb+lilypond-book+ may freely mix music and text.
82 c2 g'2 \times 2/3 { f8 e d } c'2 g4
86 Options are put in brackets.
88 \begin[fragment,quote,staffsize=26,verbatim]{lilypond}
92 Larger examples can be put into a separate file, and introduced with
95 \lilypondfile[quote,noindent]{screech-boink.ly}
97 (If needed, replace screech-boink.ly by any .ly file you put in the same
98 directory as this file.)
104 @subheading Processing
106 Save the code above to a file called @file{lilybook.lytex}, then in a
109 @c keep space after @version{} so TeX doesn't choke
111 lilypond-book --output=out --pdf lilybook.lytex
112 @emph{lilypond-book (GNU LilyPond) @version{} }
113 @emph{Reading lilybook.lytex...}
114 @emph{..lots of stuff deleted..}
115 @emph{Compiling lilybook.tex...}
118 @emph{..lots of stuff deleted..}
120 @emph{(replace @command{xpdf} by your favorite PDF viewer)}
123 Running @command{lilypond-book} and @command{latex} creates a lot of
124 temporary files, which would clutter up the working directory. To
125 remedy this, use the @code{--output=@var{dir}} option. It will create
126 the files in a separate subdirectory @file{dir}.
128 Finally the result of the @LaTeX{} example shown above.@footnote{This
129 tutorial is processed with Texinfo, so the example gives slightly
130 different results in layout.} This finishes the tutorial section.
136 Documents for @command{lilypond-book} may freely mix music and text.
141 c2 g'2 \times 2/3 { f8 e d } c'2 g4
145 Options are put in brackets.
147 @lilypond[fragment,quote,staffsize=26,verbatim]
151 Larger examples can be put into a separate file, and introduced with
152 @code{\lilypondfile}.
154 @lilypondfile[quote,noindent]{screech-boink.ly}
159 @node Integrating music and text
160 @section Integrating music and text
162 Here we explain how to integrate LilyPond with various output formats.
174 @LaTeX{} is the de-facto standard for publishing layouts in the exact
175 sciences. It is built on top of the @TeX{} typesetting engine,
176 providing the best typography available anywhere.
179 @uref{http://@/www@/.ctan@/.org/@/tex@/-archive/@/info/@/lshort/@/english/,
180 @emph{The Not So Short Introduction to @LaTeX{}}} for an overview on how
183 Music is entered using
186 \begin[options,go,here]@{lilypond@}
195 \lilypondfile[options,go,here]@{@var{filename}@}
202 \lilypond@{ YOUR LILYPOND CODE @}
205 Running @command{lilypond-book} yields a file that can be further
206 processed with @LaTeX{}.
208 We show some examples here. The @code{lilypond} environment
211 \begin[quote,fragment,staffsize=26]@{lilypond@}
219 @lilypond[quote,fragment,staffsize=26]
226 \lilypond[quote,fragment,staffsize=11]@{<c' e' g'>@}
232 @lilypond[quote,fragment,staffsize=11]{<c' e' g'>}
235 Currently, you cannot include @code{@{} or @code{@}} within
236 @code{\lilypond@{@}}, so this command is only useful with the
237 @code{fragment} option.
239 The default line width of the music will be adjusted by examining the
240 commands in the document preamble, the part of the document before
241 @code{\begin@{document@}}. The @command{lilypond-book} command sends
242 these to @LaTeX{} to find out how wide the text is. The line width for
243 the music fragments is then adjusted to the text width. Note that this
244 heuristic algorithm can fail easily; in such cases it is necessary to
245 use the @code{line-width} music fragment option.
247 @cindex titling and lilypond-book
248 @cindex \header in @LaTeX{} documents
250 Each snippet will call the following macros if they have been defined by
254 @item @code{\preLilyPondExample} called before the music,
256 @item @code{\postLilyPondExample} called after the music,
258 @item @code{\betweenLilyPondSystem[1]} is called between systems if
259 @code{lilypond-book} has split the snippet into several postscript
260 files. It must be defined as taking one parameter and will be
261 passed the number of files already included in this snippet.
262 The default is to simply insert a @code{\linebreak}.
268 @cindex Latex, feta symbols
271 To include feta symbols (such as flat, segno, etc) in a LaTeX
272 document, use @code{\input@{titledefs@}}
275 \documentclass[a4paper]@{article@}
286 The font symbol names are defined in the file feta20.tex; to find
287 the location of this file, use the command
297 Sometimes it is useful to display music elements (such as ties and slurs)
298 as if they continued after the end of the fragment. This can be done by
299 breaking the staff and suppressing inclusion of the rest of the LilyPond
302 In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that
303 inclusion of other systems is terminated once the required number of
304 systems are included. Since @code{\betweenLilypondSystem} is first
305 called @emph{after} the first system, including only the first system
309 \def\betweenLilyPondSystem#1@{\endinput@}
311 \begin[fragment]@{lilypond@}
312 c'1\( e'( c'~ \break c' d) e f\)
316 If a greater number of systems is requested, a @TeX{} conditional must
317 be used before the @code{\endinput}. In this example, replace @q{2} by
318 the number of systems you want in the output,
321 \def\betweenLilyPondSystem#1@{
322 \ifnum##1<2\else\endinput\fi
326 Remember that the definition of @code{\betweenLilyPondSystem} is
327 effective until @TeX{} quits the current group (such as the @LaTeX{}
328 environment) or is overridden by another definition (which is, in
329 most cases, for the rest of the document). To reset your
333 \let\betweenLilyPondSystem\undefined
337 in your @LaTeX{} source.
339 This may be simplified by defining a @TeX{} macro
342 \def\onlyFirstNSystems#1@{
343 \def\betweenLilyPondSystem##1@{\ifnum##1<#1\else\endinput\fi@}
348 and then saying only how many systems you want before each fragment,
351 \onlyFirstNSystems@{3@}
352 \begin@{lilypond@}...\end@{lilypond@}
353 \onlyFirstNSystems@{1@}
354 \begin@{lilypond@}...\end@{lilypond@}
358 There are specific @command{lilypond-book} command line options and
359 other details to know when processing @LaTeX{} documents, see
360 @ref{Invoking lilypond-book}.
366 Texinfo is the standard format for documentation of the GNU project. An
367 example of a Texinfo document is this manual. The HTML, PDF, and Info
368 versions of the manual are made from the Texinfo document.
370 In the input file, music is specified with
373 @@lilypond[options,go,here]
382 @@lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
389 @@lilypondfile[options,go,here]@{@var{filename}@}
392 When @command{lilypond-book} is run on it, this results in a Texinfo
393 file (with extension @file{.texi}) containing @code{@@image} tags for
394 HTML, Info and printed output. @command{lilypond-book} generates images
395 of the music in EPS and PDF formats for use in the printed output, and
396 in PNG format for use in HTML and Info output.
398 We show two simple examples here. A @code{lilypond} environment
416 @@lilypond[fragment,staffsize=11]@{<c' e' g'>@}
422 @lilypond[fragment,staffsize=11]{<c' e' g'>}
424 Contrary to @LaTeX{}, @code{@@lilypond@{...@}} does not generate an
425 in-line image. It always gets a paragraph of its own.
431 Music is entered using
434 <lilypond fragment relative=2>
435 \key c \minor c4 es g2
440 @command{lilypond-book} then produces an HTML file with appropriate image
441 tags for the music fragments:
443 @lilypond[fragment,relative=2]
444 \key c \minor c4 es g2
447 For inline pictures, use @code{<lilypond ... />}, where the options
448 are separated by a colon from the music, for example
451 Some music in <lilypond relative=2: a b c/> a line of text.
454 To include separate files, say
457 <lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
460 @cindex titling in HTML
461 @cindex preview image
467 For inserting LilyPond snippets it is good to keep the conformity of our
468 DocBook document, thus allowing us to use DocBook editors, validation
469 etc. So we don't use custom tags, only specify a convention based on the
470 standard DocBook elements.
472 @subheading Common conventions
474 For inserting all type of snippets we use the @code{mediaobject} and
475 @code{inlinemediaobject} element, so our snippets can be formatted
476 inline or not inline. The snippet formatting options are always
477 provided in the @code{role} property of the innermost element (see in
478 next sections). Tags are chosen to allow DocBook editors format the
479 content gracefully. The DocBook files to be processed with
480 @command{lilypond-book} should have the extension @file{.lyxml}.
482 @subheading Including a LilyPond file
484 This is the most simple case. We must use the @file{.ly} extension for
485 the included file, and insert it as a standard @code{imageobject}, with
486 the following structure:
491 <imagedata fileref="music1.ly" role="printfilename" />
496 Note that you can use mediaobject or inlinemediaobject as the outermost
499 @subheading Including LilyPond code
501 Including LilyPond code is possible by using a @code{programlisting},
502 where the language is set to @code{lilypond} with the following
508 <programlisting language="lilypond" role="fragment verbatim staffsize=16 ragged-right relative=2">
509 \context Staff \with @{
510 \remove Time_signature_engraver
511 \remove Clef_engraver@}
518 As you can see, the outermost element is a @code{mediaobject} or
519 @code{inlinemediaobject}, and there is a @code{textobject} containing
520 the @code{programlisting} inside.
522 @subheading Processing the DocBook document
524 Running @command{lilypond-book} on our @file{.lyxml} file will create a
525 valid DocBook document to be further processed with @file{.xml}
526 extension. If you use
527 @uref{http://@/dblatex@/.sourceforge@/.net@/,dblatex}, it will create a
528 PDF file from this document automatically. For HTML (HTML Help,
529 JavaHelp etc.) generation you can use the official DocBook XSL
530 stylesheets, however, it is possible that you have to make some
531 customization for it.
534 @node Music fragment options
535 @section Music fragment options
537 In the following, a @q{LilyPond command} refers to any command described
538 in the previous sections which is handled by @command{lilypond-book} to
539 produce a music snippet. For simplicity, LilyPond commands are only
540 shown in @LaTeX{} syntax.
542 Note that the option string is parsed from left to right; if an option
543 occurs multiple times, the last one is taken.
545 The following options are available for LilyPond commands:
548 @item staffsize=@var{ht}
549 Set staff size to @var{ht}, which is measured in points.
552 Produce ragged-right lines with natural spacing, i.e.,
553 @code{ragged-right = ##t} is added to the LilyPond snippet. This is the
554 default for the @code{\lilypond@{@}} command if no @code{line-width}
555 option is present. It is also the default for the @code{lilypond}
556 environment if the @code{fragment} option is set, and no line width is
557 explicitly specified.
559 @c does this option still exist in lilypond? -jm
561 Produce lines with packed spacing, i.e., @code{packed = ##t} is added
562 to the LilyPond snippet.
565 @itemx line-width=@var{size}\@var{unit}
566 Set line width to @var{size}, using @var{unit} as units. @var{unit} is
567 one of the following strings: @code{cm}, @code{mm}, @code{in}, or
568 @code{pt}. This option affects LilyPond output (this is, the staff
569 length of the music snippet), not the text layout.
571 If used without an argument, set line width to a default value (as
572 computed with a heuristic algorithm).
574 If no @code{line-width} option is given, @command{lilypond-book} tries to
575 guess a default for @code{lilypond} environments which don't use the
576 @code{ragged-right} option.
579 Do not print the time signature, and turns off the timing (key signature,
580 bar lines) in the score.
583 Make @command{lilypond-book} add some boilerplate code so that you can
591 without @code{\layout}, @code{\score}, etc.
594 Do not add additional code to complete LilyPond code in music snippets.
595 Since this is the default, @code{nofragment} is redundant normally.
597 @item indent=@var{size}\@var{unit}
598 Set indentation of the first music system to @var{size}, using
599 @var{unit} as units. @var{unit} is one of the following strings:
600 @code{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
601 LilyPond, not the text layout.
604 Set indentation of the first music system to zero. This option affects
605 LilyPond, not the text layout. Since no indentation is the default,
606 @code{noindent} is redundant normally.
609 Reduce line length of a music snippet by @math{2*0.4}@dmn{in} and put
610 the output into a quotation block. The value @q{0.4@dmn{in}} can be
611 controlled with the @code{exampleindent} option.
614 Set the amount by which the @code{quote} option indents a music snippet.
617 @itemx relative=@var{n}
618 Use relative octave mode. By default, notes are specified relative to
619 middle@tie{}C. The optional integer argument specifies the octave of
620 the starting note, where the default @code{1} is middle C.
623 LilyPond also uses @command{lilypond-book} to produce its own
624 documentation. To do that, some more obscure music fragment options are
629 The argument of a LilyPond command is copied to the output file and
630 enclosed in a verbatim block, followed by any text given with the
631 @code{intertext} option (not implemented yet); then the actual music is
632 displayed. This option does not work well with @code{\lilypond@{@}} if
633 it is part of a paragraph.
635 If @code{verbatim} is used in a @code{lilypondfile} command, it is
636 possible to enclose verbatim only a part of the source file. If the
637 source file contain a comment containing @samp{begin verbatim} (without
638 quotes), quoting the source in the verbatim block will start after the
639 last occurrence of such a comment; similarly, quoting the source verbatim
640 will stop just before the first occurrence of a comment containing
641 @samp{end verbatim}, it there is any. In the following source file
642 example, the music will be interpreted in relative mode, but the
643 verbatim quote will not show the @code{relative} block, i.e.
646 \relative c' @{ % begin verbatim
653 will be printed with a verbatim block like
661 (Only for Texinfo output.) Prepend line @code{\version
662 @@w@{"@@version@{@}"@}} to @code{verbatim} output.
665 (Only for Texinfo output.) If @command{lilypond} is called with the
666 @option{--header=@/texidoc} option, and the file to be processed is
667 called @file{foo@/.ly}, it creates a file @file{foo@/.texidoc} if there
668 is a @code{texidoc} field in the @code{\header}. The @code{texidoc}
669 option makes @command{lilypond-book} include such files, adding its
670 contents as a documentation block right before the music snippet.
672 Assuming the file @file{foo@/.ly} contains
676 texidoc = "This file demonstrates a single note."
682 and we have this in our Texinfo document @file{test.texinfo}
685 @@lilypondfile[texidoc]@{foo.ly@}
689 the following command line gives the expected result
692 lilypond-book --process="lilypond --format=tex --tex \
693 --header=texidoc test.texinfo
696 Most LilyPond test documents (in the @file{input} directory of the
697 distribution) are small @file{.ly} files which look exactly like this.
700 (Only for Texinfo output.) This option is similar to quote, but only
701 the music snippet (and the optional verbatim block implied by
702 @code{verbatim} option) is put into a quotation block. This option is
703 useful if you want to @code{quote} the music snippet but not the
704 @code{texidoc} documentation block.
707 If a LilyPond input file is included with @code{\lilypondfile}, print
708 the file name right before the music snippet. For HTML output, this
709 is a link. Only the base name of the file is printed, i.e. the
710 directory part of the file path is stripped.
713 This option includes fonts in all of the generated EPS-files for this
714 snippet. This should be used if the snippet uses any font that LaTeX
715 cannot find on its own.
720 @node Invoking lilypond-book
721 @section Invoking @command{lilypond-book}
723 @command{lilypond-book} produces a file with one of the following
724 extensions: @file{.tex}, @file{.texi}, @file{.html} or @file{.xml},
725 depending on the output format. All of @file{.tex}, @file{.texi} and
726 @file{.xml} files need further processing.
728 @subheading Format-specific instructions
730 @subsubheading @LaTeX{}
732 There are two ways of processing your @LaTeX{} document for printing or
733 publishing: getting a PDF file directly with PDF@LaTeX{}, or getting a
734 PostScript file with @LaTeX{} via a DVI to PostScript translator like
735 @command{dvips}. The first way is simpler and recommended@footnote{Note
736 that PDF@LaTeX{} and @LaTeX{} may not be both usable to compile any
737 @LaTeX{} document, that is why we explain the two ways.}, and whichever
738 way you use, you can easily convert between PostScript and PDF with
739 tools, like @command{ps2pdf} and @command{pdf2ps} included in
742 To produce a PDF file through PDF@LaTeX{}, use
745 lilypond-book --pdf yourfile.pdftex
746 pdflatex yourfile.tex
749 @cindex outline fonts
752 @cindex invoking dvips
753 To produce PDF output via @LaTeX{}/@command{dvips}/@command{ps2pdf}, you
757 lilypond-book yourfile.lytex
759 dvips -Ppdf yourfile.dvi
764 The @file{.dvi} file created by this process will not contain
765 note heads. This is normal; if you follow the instructions, they
766 will be included in the @file{.ps} and @file{.pdf} files.
768 Running @command{dvips} may produce some warnings about fonts; these
769 are harmless and may be ignored. If you are running @command{latex} in
770 twocolumn mode, remember to add @code{-t landscape} to the
771 @command{dvips} options.
773 @subsubheading Texinfo
775 To produce a Texinfo document (in any output format), follow the normal
776 procedures for Texinfo; this is, either call @command{texi2pdf} or
777 @command{texi2dvi} or @command{makeinfo}, depending on the output format
780 @xref{Format with texi2dvi, , , texinfo, GNU Texinfo}, and @ref{Creating
781 an Info File, , , texinfo, GNU Texinfo}.
784 See the documentation of Texinfo for further details.
788 @subheading Command line options
790 @command{lilypond-book} accepts the following command line options:
793 @item -f @var{format}
794 @itemx --format=@var{format}
795 Specify the document type to process: @code{html}, @code{latex},
796 @code{texi} (the default) or @code{docbook}. If this option is missing,
797 @command{lilypond-book} tries to detect the format automatically, see
798 @ref{Filename extensions}. Currently, @code{texi} is the same as
801 @c This complicated detail is not implemented, comment it out -jm
803 The @code{texi} document type produces a Texinfo file with music
804 fragments in the printed output only. For getting images in the HTML
805 version, the format @code{texi-html} must be used instead.
808 @item -F @var{filter}
809 @itemx --filter=@var{filter}
810 Pipe snippets through @var{filter}. @code{lilypond-book} will
811 not --filter and --process at the same time. For example,
814 lilypond-book --filter='convert-ly --from=2.0.0 -' my-book.tely
819 Print a short help message.
822 @itemx --include=@var{dir}
823 Add @var{dir} to the include path. @command{lilypond-book} also looks
824 for already compiled snippets in the include path, and does not write
825 them back to the output directory, so in some cases it is necessary to
826 invoke further processing commands such as @command{makeinfo} or
827 @command{latex} with the same @code{-I @var{dir}} options.
830 @itemx --output=@var{dir}
831 Place generated files in directory @var{dir}. Running
832 @command{lilypond-book} generates lots of small files that LilyPond will
833 process. To avoid all that garbage in the source directory, use the
834 @option{--output} command line option, and change to that directory
835 before running @command{latex} or @command{makeinfo}.
838 lilypond-book --output=out yourfile.lytex
843 @itemx --skip-lily-check
844 Do not fail if no lilypond output is found. It is used for LilyPond
845 Info documentation without images.
847 @itemx --skip-png-check
848 Do not fail if no PNG images are found for EPS files. It is used for
849 LilyPond Info documentation without images.
851 @itemx --lily-output-dir=@var{dir}
852 Write lily-XXX files to directory @var{dir}, link into @code{--output}
853 directory. Use this option to save building time for documents in
854 different directories which share a lot of identical snippets.
856 @itemx --info-images-dir=@var{dir}
857 Format Texinfo output so that Info will look for images of music in
860 @itemx --latex-program=@var{prog}
861 Run executable @command{prog} instead of @command{latex}. This is
862 useful if your document is processed with @command{xelatex}, for
865 @itemx --left-padding=@var{amount}
866 Pad EPS boxes by this much. @var{amount} is measured in millimeters,
867 and is 3.0 by default. This option should be used if the lines of
868 music stick out of the right margin.
870 The width of a tightly clipped systems can vary, due to notation
871 elements that stick into the left margin, such as bar numbers and
872 instrument names. This option will shorten each line and move each
873 line to the right by the same amount.
876 @item -P @var{process}
877 @itemx --process=@var{command}
878 Process LilyPond snippets using @var{command}. The default command is
879 @code{lilypond}. @code{lilypond-book} will not @code{--filter} and
880 @code{--process} at the same time.
883 Create PDF files for use with PDFLaTeX.
891 Print version information.
896 The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
897 @LaTeX{} commands that change margins and line widths after the preamble
900 Only the first @code{\score} of a LilyPond block is processed.
903 @node Filename extensions
904 @section Filename extensions
906 You can use any filename extension for the input file, but if you do not
907 use the recommended extension for a particular format you may need to
908 manually specify the output format; for details, see @ref{Invoking
909 lilypond-book}. Otherwise, @command{lilypond-book} automatically
910 selects the output format based on the input filename's extension.
913 @multitable @columnfractions .2 .5
914 @item @strong{extension} @tab @strong{output format}
916 @item @file{.html} @tab HTML
917 @item @file{.itely} @tab Texinfo
918 @item @file{.latex} @tab @LaTeX{}
919 @item @file{.lytex} @tab @LaTeX{}
920 @item @file{.lyxml} @tab DocBook
921 @item @file{.tely} @tab Texinfo
922 @item @file{.tex} @tab @LaTeX{}
923 @item @file{.texi} @tab Texinfo
924 @item @file{.texinfo} @tab Texinfo
925 @item @file{.xml} @tab HTML
929 If you use the same filename extension for the input file than the
930 extension @command{lilypond-book} uses for the output file, and if the
931 input file is in the same directory as @command{lilypond-book} working
932 directory, you must use @code{--output} option to make
933 @command{lilypond-book} running, otherwise the will exit with an error
934 message like @qq{Output would overwrite input file}.
937 @node Alternate methods of mixing text and music
938 @section Alternative methods of mixing text and music
940 This section shows methods to integrate text and music, different than
941 the automated method with @command{lilypond-book}.
944 * Many quotes from a large score::
945 * Inserting LilyPond output into OpenOffice.org::
946 * Inserting LilyPond output into other programs::
949 @node Many quotes from a large score
950 @subsection Many quotes from a large score
952 If you need to quote many fragments from a large score, you can also use
953 the clip systems feature, see @ruser{Extracting fragments of notation}.
956 @node Inserting LilyPond output into OpenOffice.org
957 @subsection Inserting LilyPond output into OpenOffice.org
959 @cindex OpenOffice.org
961 LilyPond notation can be added to OpenOffice.org with
962 @uref{http://@/ooolilypond@/.sourceforge@/.net@/,OOoLilyPond}.
965 @node Inserting LilyPond output into other programs
966 @subsection Inserting LilyPond output into other programs
968 To insert LilyPond output in other programs, use @code{lilypond}
969 instead of @code{lilypond-book}. Each example must be created
970 individually and added to the document; consult the documentation for
971 that program. Most programs will be able to insert LilyPond output in
972 @file{PNG}, @file{EPS}, or @file{PDF} formats.
974 To reduce the white space around your LilyPond score, use
975 the following options
983 bookTitleMarkup = ##f
984 scoreTitleMarkup = ##f
990 To produce a useful EPS file, use
993 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts myfile.ly