1 @c -*- coding: utf-8; mode: texinfo; -*-
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 Running @command{lilypond-book}
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
28 on the command line; for more information, see @ref{Command-line
29 usage}. If you have MacOS 10.3 or 10.4 and you have trouble running
30 @code{lilypond-book}, see FIXME FIXME @c @ref{Setup for MacOS X}.
32 This procedure may be applied to @LaTeX{}, HTML, Texinfo or DocBook
41 @cindex documents, adding music to
42 @cindex HTML, music in
43 @cindex Texinfo, music in
44 @cindex DocBook, music in
45 @cindex @LaTeX{}, music in
48 * An example of a musicological document::
49 * Integrating music and text::
50 * Music fragment options::
51 * Invoking lilypond-book::
52 * Filename extensions::
53 * Alternate methods of mixing text and music::
57 @node An example of a musicological document
58 @section An example of a musicological document
61 Some texts contain music examples. These texts are musicological
62 treatises, songbooks, or manuals like this. Such texts can be made by
63 hand, simply by importing a PostScript figure into the word processor.
64 However, there is an automated procedure to reduce the amount of work
65 involved in HTML, @LaTeX{}, Texinfo and DocBook documents.
67 A script called @code{lilypond-book} will extract the music fragments,
68 format them, and put back the resulting notation. Here we show a small
69 example for use with @LaTeX{}. The example also contains explanatory
70 text, so we will not comment on it further.
76 \documentclass[a4paper]{article}
80 Documents for \verb+lilypond-book+ may freely mix music and text.
85 c2 g'2 \times 2/3 { f8 e d } c'2 g4
89 Options are put in brackets.
91 \begin[fragment,quote,staffsize=26,verbatim]{lilypond}
95 Larger examples can be put into a separate file, and introduced with
98 \lilypondfile[quote,noindent]{screech-boink.ly}
100 (If needed, replace screech-boink.ly by any .ly file you put in the same
101 directory as this file.)
107 @subheading Processing
109 Save the code above to a file called @file{lilybook.lytex}, then in a
112 @c keep space after @version{} so TeX doesn't choke
114 lilypond-book --output=out --pdf lilybook.lytex
115 @emph{lilypond-book (GNU LilyPond) @version{} }
116 @emph{Reading lilybook.lytex...}
117 @emph{..lots of stuff deleted..}
118 @emph{Compiling lilybook.tex...}
121 @emph{..lots of stuff deleted..}
123 @emph{(replace @command{xpdf} by your favorite PDF viewer)}
126 Running @command{lilypond-book} and @command{latex} creates a lot of
127 temporary files, which would clutter up the working directory. To
128 remedy this, use the @code{--output=@var{dir}} option. It will create
129 the files in a separate subdirectory @file{dir}.
131 Finally the result of the @LaTeX{} example shown above.@footnote{This
132 tutorial is processed with Texinfo, so the example gives slightly
133 different results in layout.} This finishes the tutorial section.
139 Documents for @command{lilypond-book} may freely mix music and text.
144 c2 g'2 \times 2/3 { f8 e d } c'2 g4
148 Options are put in brackets.
150 @lilypond[fragment,quote,staffsize=26,verbatim]
154 Larger examples can be put into a separate file, and introduced with
155 @code{\lilypondfile}.
157 @lilypondfile[quote,noindent]{screech-boink.ly}
162 @node Integrating music and text
163 @section Integrating music and text
165 Here we explain how to integrate LilyPond with various output formats.
177 @LaTeX{} is the de-facto standard for publishing layouts in the exact
178 sciences. It is built on top of the @TeX{} typesetting engine,
179 providing the best typography available anywhere.
182 @uref{http://@/www@/.ctan@/.org/@/tex@/-archive/@/info/@/lshort/@/english/,
183 @emph{The Not So Short Introduction to @LaTeX{}}} for an overview on how
186 Music is entered using
189 \begin[options,go,here]@{lilypond@}
198 \lilypondfile[options,go,here]@{@var{filename}@}
205 \lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
208 Additionally, @code{\lilypondversion} displays the current version
210 Running @command{lilypond-book} yields a file that can be further
211 processed with @LaTeX{}.
213 We show some examples here. The @code{lilypond} environment
216 \begin[quote,fragment,staffsize=26]@{lilypond@}
224 @lilypond[quote,fragment,staffsize=26]
231 \lilypond[quote,fragment,staffsize=11]@{<c' e' g'>@}
237 @lilypond[quote,fragment,staffsize=11]{<c' e' g'>}
240 Currently, you cannot include @code{@{} or @code{@}} within
241 @code{\lilypond@{@}}, so this command is only useful with the
242 @code{fragment} option.
244 The default line width of the music will be adjusted by examining the
245 commands in the document preamble, the part of the document before
246 @code{\begin@{document@}}. The @command{lilypond-book} command sends
247 these to @LaTeX{} to find out how wide the text is. The line width for
248 the music fragments is then adjusted to the text width. Note that this
249 heuristic algorithm can fail easily; in such cases it is necessary to
250 use the @code{line-width} music fragment option.
252 @cindex titling and lilypond-book
253 @cindex \header in @LaTeX{} documents
255 Each snippet will call the following macros if they have been defined by
259 @item @code{\preLilyPondExample} called before the music,
261 @item @code{\postLilyPondExample} called after the music,
263 @item @code{\betweenLilyPondSystem[1]} is called between systems if
264 @code{lilypond-book} has split the snippet into several PostScript
265 files. It must be defined as taking one parameter and will be
266 passed the number of files already included in this snippet.
267 The default is to simply insert a @code{\linebreak}.
273 @cindex Latex, feta symbols
276 To include feta symbols (such as flat, segno, etc) in a LaTeX
277 document, use @code{\input@{titledefs@}}
280 \documentclass[a4paper]@{article@}
291 The font symbol names are defined in the file feta20.tex; to find
292 the location of this file, use the command
302 Sometimes it is useful to display music elements (such as ties and slurs)
303 as if they continued after the end of the fragment. This can be done by
304 breaking the staff and suppressing inclusion of the rest of the LilyPond
307 In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that
308 inclusion of other systems is terminated once the required number of
309 systems are included. Since @code{\betweenLilyPondSystem} is first
310 called @emph{after} the first system, including only the first system
314 \def\betweenLilyPondSystem#1@{\endinput@}
316 \begin[fragment]@{lilypond@}
317 c'1\( e'( c'~ \break c' d) e f\)
321 If a greater number of systems is requested, a @TeX{} conditional must
322 be used before the @code{\endinput}. In this example, replace @q{2} by
323 the number of systems you want in the output.
326 \def\betweenLilyPondSystem#1@{
327 \ifnum##1<2\else\expandafter\endinput\fi
332 (Since @code{\endinput} immediately stops the processing of the current
333 input file we need @code{\expandafter} to delay the call of @code{\endinput}
334 after executing @code{\fi} so that the @code{\if}-@code{\fi} clause is
337 Remember that the definition of @code{\betweenLilyPondSystem} is
338 effective until @TeX{} quits the current group (such as the @LaTeX{}
339 environment) or is overridden by another definition (which is, in
340 most cases, for the rest of the document). To reset your
344 \let\betweenLilyPondSystem\undefined
348 in your @LaTeX{} source.
350 This may be simplified by defining a @TeX{} macro
353 \def\onlyFirstNSystems#1@{
354 \def\betweenLilyPondSystem##1@{%
355 \ifnum##1<#1\else\expandafter\endinput\fi@}
360 and then saying only how many systems you want before each fragment,
363 \onlyFirstNSystems@{3@}
364 \begin@{lilypond@}...\end@{lilypond@}
365 \onlyFirstNSystems@{1@}
366 \begin@{lilypond@}...\end@{lilypond@}
371 There are specific @command{lilypond-book} command line options and
372 other details to know when processing @LaTeX{} documents, see
373 @ref{Invoking lilypond-book}.
379 Texinfo is the standard format for documentation of the GNU project. An
380 example of a Texinfo document is this manual. The HTML, PDF, and Info
381 versions of the manual are made from the Texinfo document.
383 In the input file, music is specified with
386 @@lilypond[options,go,here]
395 @@lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
402 @@lilypondfile[options,go,here]@{@var{filename}@}
405 Additionally, @code{@@lilypondversion} displays the current version
408 When @command{lilypond-book} is run on it, this results in a Texinfo
409 file (with extension @file{.texi}) containing @code{@@image} tags for
410 HTML, Info and printed output. @command{lilypond-book} generates images
411 of the music in EPS and PDF formats for use in the printed output, and
412 in PNG format for use in HTML and Info output.
414 We show two simple examples here. A @code{lilypond} environment
432 @@lilypond[fragment,staffsize=11]@{<c' e' g'>@}
438 @lilypond[fragment,staffsize=11]{<c' e' g'>}
440 Contrary to @LaTeX{}, @code{@@lilypond@{...@}} does not generate an
441 in-line image. It always gets a paragraph of its own.
447 Music is entered using
450 <lilypond fragment relative=2>
451 \key c \minor c4 es g2
455 @command{lilypond-book} then produces an HTML file with appropriate image
456 tags for the music fragments:
458 @lilypond[fragment,relative=2]
459 \key c \minor c4 es g2
462 For inline pictures, use @code{<lilypond ... />}, where the options
463 are separated by a colon from the music, for example
466 Some music in <lilypond relative=2: a b c/> a line of text.
470 To include separate files, say
473 <lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
476 Additionally, @code{<lilypondversion/>} displays the current version
480 @cindex titling in HTML
481 @cindex preview image
487 For inserting LilyPond snippets it is good to keep the conformity of our
488 DocBook document, thus allowing us to use DocBook editors, validation
489 etc. So we don't use custom tags, only specify a convention based on the
490 standard DocBook elements.
492 @subheading Common conventions
494 For inserting all type of snippets we use the @code{mediaobject} and
495 @code{inlinemediaobject} element, so our snippets can be formatted
496 inline or not inline. The snippet formatting options are always
497 provided in the @code{role} property of the innermost element (see in
498 next sections). Tags are chosen to allow DocBook editors format the
499 content gracefully. The DocBook files to be processed with
500 @command{lilypond-book} should have the extension @file{.lyxml}.
502 @subheading Including a LilyPond file
504 This is the most simple case. We must use the @file{.ly} extension for
505 the included file, and insert it as a standard @code{imageobject}, with
506 the following structure:
511 <imagedata fileref="music1.ly" role="printfilename" />
516 Note that you can use @code{mediaobject} or @code{inlinemediaobject}
517 as the outermost element as you wish.
519 @subheading Including LilyPond code
521 Including LilyPond code is possible by using a @code{programlisting},
522 where the language is set to @code{lilypond} with the following
528 <programlisting language="lilypond" role="fragment verbatim staffsize=16 ragged-right relative=2">
529 \context Staff \with @{
530 \remove Time_signature_engraver
531 \remove Clef_engraver@}
538 As you can see, the outermost element is a @code{mediaobject} or
539 @code{inlinemediaobject}, and there is a @code{textobject} containing
540 the @code{programlisting} inside.
542 @subheading Processing the DocBook document
544 Running @command{lilypond-book} on our @file{.lyxml} file will create a
545 valid DocBook document to be further processed with @file{.xml}
546 extension. If you use
547 @uref{http://@/dblatex@/.sourceforge@/.net@/,dblatex}, it will create a
548 PDF file from this document automatically. For HTML (HTML Help,
549 JavaHelp etc.) generation you can use the official DocBook XSL
550 stylesheets, however, it is possible that you have to make some
551 customization for it.
554 @node Music fragment options
555 @section Music fragment options
557 In the following, a @q{LilyPond command} refers to any command described
558 in the previous sections which is handled by @command{lilypond-book} to
559 produce a music snippet. For simplicity, LilyPond commands are only
560 shown in @LaTeX{} syntax.
562 Note that the option string is parsed from left to right; if an option
563 occurs multiple times, the last one is taken.
565 The following options are available for LilyPond commands:
568 @item staffsize=@var{ht}
569 Set staff size to @var{ht}, which is measured in points.
572 Produce ragged-right lines with natural spacing, i.e.,
573 @code{ragged-right = ##t} is added to the LilyPond snippet. This is the
574 default for the @code{\lilypond@{@}} command if no @code{line-width}
575 option is present. It is also the default for the @code{lilypond}
576 environment if the @code{fragment} option is set, and no line width is
577 explicitly specified.
580 For single-line snippets, allow the staff length to be stretched to
581 equal that of the line width, i.e., @code{ragged-right = ##f} is
582 added to the LilyPond snippet.
585 @itemx line-width=@var{size}\@var{unit}
586 Set line width to @var{size}, using @var{unit} as units. @var{unit} is
587 one of the following strings: @code{cm}, @code{mm}, @code{in}, or
588 @code{pt}. This option affects LilyPond output (this is, the staff
589 length of the music snippet), not the text layout.
591 If used without an argument, set line width to a default value (as
592 computed with a heuristic algorithm).
594 If no @code{line-width} option is given, @command{lilypond-book} tries to
595 guess a default for @code{lilypond} environments which don't use the
596 @code{ragged-right} option.
599 Do not print the time signature, and turns off the timing (time signature,
600 bar lines) in the score.
603 Make @command{lilypond-book} add some boilerplate code so that you can
611 without @code{\layout}, @code{\score}, etc.
614 Do not add additional code to complete LilyPond code in music snippets.
615 Since this is the default, @code{nofragment} is redundant normally.
617 @item indent=@var{size}\@var{unit}
618 Set indentation of the first music system to @var{size}, using
619 @var{unit} as units. @var{unit} is one of the following strings:
620 @code{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
621 LilyPond, not the text layout.
624 Set indentation of the first music system to zero. This option affects
625 LilyPond, not the text layout. Since no indentation is the default,
626 @code{noindent} is redundant normally.
629 Reduce line length of a music snippet by @math{2*0.4}@dmn{in} and put
630 the output into a quotation block. The value @q{0.4@dmn{in}} can be
631 controlled with the @code{exampleindent} option.
634 Set the amount by which the @code{quote} option indents a music snippet.
637 @itemx relative=@var{n}
638 Use relative octave mode. By default, notes are specified relative to
639 middle@tie{}C. The optional integer argument specifies the octave of
640 the starting note, where the default @code{1} is middle C.
641 @code{relative} option only works when @code{fragment} option is set,
642 so @code{fragment} is automatically implied by @code{relative},
643 regardless of the presence of any @code{(no)fragment} option in the
647 LilyPond also uses @command{lilypond-book} to produce its own
648 documentation. To do that, some more obscure music fragment options are
653 The argument of a LilyPond command is copied to the output file and
654 enclosed in a verbatim block, followed by any text given with the
655 @code{intertext} option (not implemented yet); then the actual music is
656 displayed. This option does not work well with @code{\lilypond@{@}} if
657 it is part of a paragraph.
659 If @code{verbatim} is used in a @code{lilypondfile} command, it is
660 possible to enclose verbatim only a part of the source file. If the
661 source file contain a comment containing @samp{begin verbatim} (without
662 quotes), quoting the source in the verbatim block will start after the
663 last occurrence of such a comment; similarly, quoting the source verbatim
664 will stop just before the first occurrence of a comment containing
665 @samp{end verbatim}, if there is any. In the following source file
666 example, the music will be interpreted in relative mode, but the
667 verbatim quote will not show the @code{relative} block, i.e.
670 \relative c' @{ % begin verbatim
677 will be printed with a verbatim block like
685 If you would like to translate comments and variable names in verbatim
686 output but not in the sources, you may set the environment variable
687 @code{LYDOC_LOCALEDIR} to a directory path; the directory should
688 contain a tree of @file{.mo} message catalogs with @code{lilypond-doc}
692 (Only for Texinfo output.) Prepend line @code{\version
693 @@w@{"@@version@{@}"@}} to @code{verbatim} output.
696 (Only for Texinfo output.) If @command{lilypond} is called with the
697 @option{--header=@/texidoc} option, and the file to be processed is
698 called @file{foo@/.ly}, it creates a file @file{foo@/.texidoc} if there
699 is a @code{texidoc} field in the @code{\header}. The @code{texidoc}
700 option makes @command{lilypond-book} include such files, adding its
701 contents as a documentation block right before the music snippet.
703 Assuming the file @file{foo@/.ly} contains
707 texidoc = "This file demonstrates a single note."
713 and we have this in our Texinfo document @file{test.texinfo}
716 @@lilypondfile[texidoc]@{foo.ly@}
720 the following command line gives the expected result
723 lilypond-book --pdf --process="lilypond \
724 -dbackend=eps --header=texidoc" test.texinfo
727 Most LilyPond test documents (in the @file{input} directory of the
728 distribution) are small @file{.ly} files which look exactly like this.
730 For localization purpose, if the Texinfo document contains
731 @code{@@documentlanguage @var{LANG}} and @file{foo@/.ly} header
732 contains a @code{texidoc@var{LANG}} field, and if @command{lilypond}
733 is called with @option{--header=@/texidoc@var{LANG}}, then
734 @file{foo@/.texidoc@var{LANG}} will be included instead of
735 @file{foo@/.texidoc}.
738 (Only for Texinfo output.) This option is similar to quote, but only
739 the music snippet (and the optional verbatim block implied by
740 @code{verbatim} option) is put into a quotation block. This option is
741 useful if you want to @code{quote} the music snippet but not the
742 @code{texidoc} documentation block.
745 (Only for Texinfo output.) This option works similarly to
746 @code{texidoc} option: if @command{lilypond} is called with the
747 @option{--header=@/doctitle} option, and the file to be processed is
748 called @file{foo@/.ly} and contains a @code{doctitle} field in the
749 @code{\header}, it creates a file @file{foo@/.doctitle}. When
750 @code{doctitle} option is used, the contents of @file{foo@/.doctitle},
751 which should be a single line of @var{text}, is inserted in the
752 Texinfo document as @code{@@lydoctitle @var{text}}.
753 @code{@@lydoctitle} should be a macro defined in the Texinfo document.
754 The same remark about @code{texidoc} processing with localized
755 languages also applies to @code{doctitle}.
758 (Only for Texinfo output.) Do not translate comments and variable
759 names in the snippet quoted verbatim.
762 If a LilyPond input file is included with @code{\lilypondfile}, print
763 the file name right before the music snippet. For HTML output, this
764 is a link. Only the base name of the file is printed, i.e. the
765 directory part of the file path is stripped.
770 @node Invoking lilypond-book
771 @section Invoking @command{lilypond-book}
773 @command{lilypond-book} produces a file with one of the following
774 extensions: @file{.tex}, @file{.texi}, @file{.html} or @file{.xml},
775 depending on the output format. All of @file{.tex}, @file{.texi} and
776 @file{.xml} files need further processing.
778 @subheading Format-specific instructions
780 @subsubheading @LaTeX{}
782 There are two ways of processing your @LaTeX{} document for printing or
783 publishing: getting a PDF file directly with PDF@LaTeX{}, or getting a
784 PostScript file with @LaTeX{} via a DVI to PostScript translator like
785 @command{dvips}. The first way is simpler and recommended@footnote{Note
786 that PDF@LaTeX{} and @LaTeX{} may not be both usable to compile any
787 @LaTeX{} document, that is why we explain the two ways.}, and whichever
788 way you use, you can easily convert between PostScript and PDF with
789 tools, like @command{ps2pdf} and @command{pdf2ps} included in
792 To produce a PDF file through PDF@LaTeX{}, use
795 lilypond-book --pdf yourfile.pdftex
796 pdflatex yourfile.tex
799 @cindex outline fonts
802 @cindex invoking dvips
803 To produce PDF output via @LaTeX{}/@command{dvips}/@command{ps2pdf}, you
807 lilypond-book yourfile.lytex
809 dvips -Ppdf yourfile.dvi
814 The @file{.dvi} file created by this process will not contain
815 note heads. This is normal; if you follow the instructions, they
816 will be included in the @file{.ps} and @file{.pdf} files.
818 Running @command{dvips} may produce some warnings about fonts; these
819 are harmless and may be ignored. If you are running @command{latex} in
820 twocolumn mode, remember to add @code{-t landscape} to the
821 @command{dvips} options.
823 @subsubheading Texinfo
825 To produce a Texinfo document (in any output format), follow the normal
826 procedures for Texinfo; this is, either call @command{texi2pdf} or
827 @command{texi2dvi} or @command{makeinfo}, depending on the output format
830 @xref{Format with texi2dvi, , , texinfo, GNU Texinfo}, and @ref{Creating
831 an Info File, , , texinfo, GNU Texinfo}.
834 See the documentation of Texinfo for further details.
838 @subheading Command line options
840 @command{lilypond-book} accepts the following command line options:
843 @item -f @var{format}
844 @itemx --format=@var{format}
845 Specify the document type to process: @code{html}, @code{latex},
846 @code{texi} (the default) or @code{docbook}. If this option is missing,
847 @command{lilypond-book} tries to detect the format automatically, see
848 @ref{Filename extensions}. Currently, @code{texi} is the same as
851 @c This complicated detail is not implemented, comment it out -jm
853 The @code{texi} document type produces a Texinfo file with music
854 fragments in the printed output only. For getting images in the HTML
855 version, the format @code{texi-html} must be used instead.
858 @item -F @var{filter}
859 @itemx --filter=@var{filter}
860 Pipe snippets through @var{filter}. @code{lilypond-book} will
861 not --filter and --process at the same time. For example,
864 lilypond-book --filter='convert-ly --from=2.0.0 -' my-book.tely
869 Print a short help message.
872 @itemx --include=@var{dir}
873 Add @var{dir} to the include path. @command{lilypond-book} also looks
874 for already compiled snippets in the include path, and does not write
875 them back to the output directory, so in some cases it is necessary to
876 invoke further processing commands such as @command{makeinfo} or
877 @command{latex} with the same @code{-I @var{dir}} options.
880 @itemx --output=@var{dir}
881 Place generated files in directory @var{dir}. Running
882 @command{lilypond-book} generates lots of small files that LilyPond will
883 process. To avoid all that garbage in the source directory, use the
884 @option{--output} command line option, and change to that directory
885 before running @command{latex} or @command{makeinfo}.
888 lilypond-book --output=out yourfile.lytex
893 @itemx --skip-lily-check
894 Do not fail if no lilypond output is found. It is used for LilyPond
895 Info documentation without images.
897 @itemx --skip-png-check
898 Do not fail if no PNG images are found for EPS files. It is used for
899 LilyPond Info documentation without images.
901 @itemx --lily-output-dir=@var{dir}
902 Write lily-XXX files to directory @var{dir}, link into @code{--output}
903 directory. Use this option to save building time for documents in
904 different directories which share a lot of identical snippets.
906 @itemx --info-images-dir=@var{dir}
907 Format Texinfo output so that Info will look for images of music in
910 @itemx --latex-program=@var{prog}
911 Run executable @command{prog} instead of @command{latex}. This is
912 useful if your document is processed with @command{xelatex}, for
915 @itemx --left-padding=@var{amount}
916 Pad EPS boxes by this much. @var{amount} is measured in millimeters,
917 and is 3.0 by default. This option should be used if the lines of
918 music stick out of the right margin.
920 The width of a tightly clipped system can vary, due to notation
921 elements that stick into the left margin, such as bar numbers and
922 instrument names. This option will shorten each line and move each
923 line to the right by the same amount.
926 @item -P @var{command}
927 @itemx --process=@var{command}
928 Process LilyPond snippets using @var{command}. The default command is
929 @code{lilypond}. @code{lilypond-book} will not @code{--filter} and
930 @code{--process} at the same time.
933 Create PDF files for use with PDF@LaTeX{}.
941 Print version information.
946 The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
947 @LaTeX{} commands that change margins and line widths after the preamble
950 Only the first @code{\score} of a LilyPond block is processed.
953 @node Filename extensions
954 @section Filename extensions
956 You can use any filename extension for the input file, but if you do not
957 use the recommended extension for a particular format you may need to
958 manually specify the output format; for details, see @ref{Invoking
959 lilypond-book}. Otherwise, @command{lilypond-book} automatically
960 selects the output format based on the input filename's extension.
963 @multitable @columnfractions .2 .5
964 @item @strong{extension} @tab @strong{output format}
966 @item @file{.html} @tab HTML
967 @item @file{.itely} @tab Texinfo
968 @item @file{.latex} @tab @LaTeX{}
969 @item @file{.lytex} @tab @LaTeX{}
970 @item @file{.lyxml} @tab DocBook
971 @item @file{.tely} @tab Texinfo
972 @item @file{.tex} @tab @LaTeX{}
973 @item @file{.texi} @tab Texinfo
974 @item @file{.texinfo} @tab Texinfo
975 @item @file{.xml} @tab HTML
979 If you use the same filename extension for the input file than the
980 extension @command{lilypond-book} uses for the output file, and if the
981 input file is in the same directory as @command{lilypond-book} working
982 directory, you must use @code{--output} option to make
983 @command{lilypond-book} running, otherwise it will exit with an error
984 message like @qq{Output would overwrite input file}.
987 @node Alternate methods of mixing text and music
988 @section Alternative methods of mixing text and music
990 This section shows methods to integrate text and music, different than
991 the automated method with @command{lilypond-book}.
994 * Many quotes from a large score::
995 * Inserting LilyPond output into OpenOffice.org::
996 * Inserting LilyPond output into other programs::
999 @node Many quotes from a large score
1000 @unnumberedsubsec Many quotes from a large score
1002 If you need to quote many fragments from a large score, you can also use
1003 the clip systems feature, see @ruser{Extracting fragments of music}.
1006 @node Inserting LilyPond output into OpenOffice.org
1007 @unnumberedsubsec Inserting LilyPond output into OpenOffice.org
1009 @cindex OpenOffice.org
1011 LilyPond notation can be added to OpenOffice.org with
1012 @uref{http://@/ooolilypond@/.sourceforge@/.net@/,OOoLilyPond}.
1015 @node Inserting LilyPond output into other programs
1016 @unnumberedsubsec Inserting LilyPond output into other programs
1018 To insert LilyPond output in other programs, use @code{lilypond}
1019 instead of @code{lilypond-book}. Each example must be created
1020 individually and added to the document; consult the documentation for
1021 that program. Most programs will be able to insert LilyPond output in
1022 @file{PNG}, @file{EPS}, or @file{PDF} formats.
1024 To reduce the white space around your LilyPond score, use
1025 the following options
1033 bookTitleMarkup = ##f
1034 scoreTitleMarkup = ##f
1040 To produce a useful @file{EPS} file, use
1043 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts myfile.ly
1046 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly