1 @c -*- coding: utf-8; mode: texinfo; documentlanguage: ja -*-
4 Translation of GIT committish: 9a65042d49324f2e3dff18c4b0858def81232eea
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..
13 @c Translators: Yoshiki Sawada
14 @c Translation status: post-GDP
16 @c Note: keep this node named so that `info lilypond-book' brings you here.
18 @chapter @command{lilypond-book}: Integrating text and music
19 @translationof lilypond-book
23 If you want to add pictures of music to a document, you can simply do it
24 the way you would do with other types of pictures. The pictures are
25 created separately, yielding PostScript output or PNG images, and those
26 are included into a @LaTeX{} or HTML document.
28 @command{lilypond-book} provides a way to automate this process: This
29 program extracts snippets of music from your document, runs
30 @command{lilypond} on them, and outputs the document with pictures
31 substituted for the music. The line width and font size definitions for
32 the music are adjusted to match the layout of your document.
34 This is a separate program from @command{lilypond} itself, and is run
35 on the command line; for more information, see @ref{コマンド ラインの使用方法}. If you have MacOS 10.3 or 10.4 and you have trouble running
36 @code{lilypond-book}, see FIXME FIXME @c @ref{MacOS X のためのセットアップ}.
38 This procedure may be applied to @LaTeX{}, HTML, Texinfo or DocBook
47 @cindex documents, adding music to
48 @cindex HTML, music in
49 @cindex Texinfo, music in
50 @cindex DocBook, music in
51 @cindex @LaTeX{}, music in
54 * An example of a musicological document::
55 * Integrating music and text::
56 * Music fragment options::
57 * Invoking lilypond-book::
58 * Filename extensions::
59 * Alternate methods of mixing text and music::
63 @node An example of a musicological document
64 @section An example of a musicological document
65 @translationof An example of a musicological document
70 Some texts contain music examples. These texts are musicological
71 treatises, songbooks, or manuals like this. Such texts can be made by
72 hand, simply by importing a PostScript figure into the word processor.
73 However, there is an automated procedure to reduce the amount of work
74 involved in HTML, @LaTeX{}, Texinfo and DocBook documents.
76 A script called @code{lilypond-book} will extract the music fragments,
77 format them, and put back the resulting notation. Here we show a small
78 example for use with @LaTeX{}. The example also contains explanatory
79 text, so we will not comment on it further.
85 \documentclass[a4paper]{article}
89 Documents for \verb+lilypond-book+ may freely mix music and text.
94 c2 e2 \times 2/3 { f8 a b } a2 e4
98 Options are put in brackets.
100 \begin{lilypond}[fragment,quote,staffsize=26,verbatim]
104 Larger examples can be put into a separate file, and introduced with
105 \verb+\lilypondfile+.
107 \lilypondfile[quote,noindent]{screech-boink.ly}
109 (If needed, replace screech-boink.ly by any .ly file you put in the same
110 directory as this file.)
116 @subheading Processing
118 Save the code above to a file called @file{lilybook.lytex}, then in a
121 @c keep space after @version{} so TeX doesn't choke
123 lilypond-book --output=out --pdf lilybook.lytex
124 @emph{lilypond-book (GNU LilyPond) @version{} }
125 @emph{Reading lilybook.lytex...}
126 @emph{..lots of stuff deleted..}
127 @emph{Compiling lilybook.tex...}
130 @emph{..lots of stuff deleted..}
132 @emph{(replace @command{xpdf} by your favorite PDF viewer)}
135 Running @command{lilypond-book} and @command{latex} creates a lot of
136 temporary files, which would clutter up the working directory. To
137 remedy this, use the @code{--output=@var{dir}} option. It will create
138 the files in a separate subdirectory @file{dir}.
140 Finally the result of the @LaTeX{} example shown above.@footnote{This
141 tutorial is processed with Texinfo, so the example gives slightly
142 different results in layout.} This finishes the tutorial section.
148 Documents for @command{lilypond-book} may freely mix music and text.
153 c2 e2 \times 2/3 { f8 a b } a2 e4
157 Options are put in brackets.
159 @lilypond[fragment,quote,staffsize=26,verbatim]
163 Larger examples can be put into a separate file, and introduced with
164 @code{\lilypondfile}.
166 @lilypondfile[quote,noindent]{screech-boink.ly}
171 @node Integrating music and text
172 @section Integrating music and text
173 @translationof Integrating music and text
177 Here we explain how to integrate LilyPond with various output formats.
192 @LaTeX{} is the de-facto standard for publishing layouts in the exact
193 sciences. It is built on top of the @TeX{} typesetting engine,
194 providing the best typography available anywhere.
197 @uref{http://@/www@/.ctan@/.org/@/tex@/-archive/@/info/@/lshort/@/english/,
198 @emph{The Not So Short Introduction to @LaTeX{}}} for an overview on how
201 Music is entered using
204 \begin@{lilypond@}[options,go,here]
213 \lilypondfile[options,go,here]@{@var{filename}@}
220 \lilypond@{ YOUR LILYPOND CODE @}
223 Additionally, @code{\lilypondversion} displays the current version
225 Running @command{lilypond-book} yields a file that can be further
226 processed with @LaTeX{}.
228 We show some examples here. The @code{lilypond} environment
231 \begin@{lilypond@}[quote,fragment,staffsize=26]
239 @lilypond[quote,fragment,staffsize=26]
246 \lilypond[quote,fragment,staffsize=11]@{<c' e' g'>@}
252 @lilypond[quote,fragment,staffsize=11]{<c' e' g'>}
255 Currently, you cannot include @code{@{} or @code{@}} within
256 @code{\lilypond@{@}}, so this command is only useful with the
257 @code{fragment} option.
259 The default line width of the music will be adjusted by examining the
260 commands in the document preamble, the part of the document before
261 @code{\begin@{document@}}. The @command{lilypond-book} command sends
262 these to @LaTeX{} to find out how wide the text is. The line width for
263 the music fragments is then adjusted to the text width. Note that this
264 heuristic algorithm can fail easily; in such cases it is necessary to
265 use the @code{line-width} music fragment option.
267 @cindex titling and lilypond-book
268 @cindex \header in @LaTeX{} documents
270 Each snippet will call the following macros if they have been defined by
274 @item @code{\preLilyPondExample} called before the music,
276 @item @code{\postLilyPondExample} called after the music,
278 @item @code{\betweenLilyPondSystem[1]} is called between systems if
279 @code{lilypond-book} has split the snippet into several PostScript
280 files. It must be defined as taking one parameter and will be
281 passed the number of files already included in this snippet.
282 The default is to simply insert a @code{\linebreak}.
288 @cindex Latex, feta symbols
291 To include feta symbols (such as flat, segno, etc) in a LaTeX
292 document, use @code{\input@{titledefs@}}
295 \documentclass[a4paper]@{article@}
306 The font symbol names are defined in the file feta20.tex; to find
307 the location of this file, use the command
317 Sometimes it is useful to display music elements (such as ties and slurs)
318 as if they continued after the end of the fragment. This can be done by
319 breaking the staff and suppressing inclusion of the rest of the LilyPond
322 In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that
323 inclusion of other systems is terminated once the required number of
324 systems are included. Since @code{\betweenLilyPondSystem} is first
325 called @emph{after} the first system, including only the first system
329 \def\betweenLilyPondSystem#1@{\endinput@}
331 \begin@{lilypond@}[fragment]
332 c'1\( e'( c'~ \break c' d) e f\)
336 If a greater number of systems is requested, a @TeX{} conditional must
337 be used before the @code{\endinput}. In this example, replace @q{2} by
338 the number of systems you want in the output,
341 \def\betweenLilyPondSystem#1@{
342 \ifnum##1<2\else\endinput\fi
346 Remember that the definition of @code{\betweenLilyPondSystem} is
347 effective until @TeX{} quits the current group (such as the @LaTeX{}
348 environment) or is overridden by another definition (which is, in
349 most cases, for the rest of the document). To reset your
353 \let\betweenLilyPondSystem\undefined
357 in your @LaTeX{} source.
359 This may be simplified by defining a @TeX{} macro
362 \def\onlyFirstNSystems#1@{
363 \def\betweenLilyPondSystem##1@{\ifnum##1<#1\else\endinput\fi@}
368 and then saying only how many systems you want before each fragment,
371 \onlyFirstNSystems@{3@}
372 \begin@{lilypond@}...\end@{lilypond@}
373 \onlyFirstNSystems@{1@}
374 \begin@{lilypond@}...\end@{lilypond@}
379 There are specific @command{lilypond-book} command line options and
380 other details to know when processing @LaTeX{} documents, see
381 @ref{Invoking lilypond-book}.
386 @translationof Texinfo
390 Texinfo is the standard format for documentation of the GNU project. An
391 example of a Texinfo document is this manual. The HTML, PDF, and Info
392 versions of the manual are made from the Texinfo document.
394 In the input file, music is specified with
397 @@lilypond[options,go,here]
406 @@lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
413 @@lilypondfile[options,go,here]@{@var{filename}@}
416 Additionally, @code{@@lilypondversion} displays the current version
419 When @command{lilypond-book} is run on it, this results in a Texinfo
420 file (with extension @file{.texi}) containing @code{@@image} tags for
421 HTML, Info and printed output. @command{lilypond-book} generates images
422 of the music in EPS and PDF formats for use in the printed output, and
423 in PNG format for use in HTML and Info output.
425 We show two simple examples here. A @code{lilypond} environment
443 @@lilypond[fragment,staffsize=11]@{<c' e' g'>@}
449 @lilypond[fragment,staffsize=11]{<c' e' g'>}
451 Contrary to @LaTeX{}, @code{@@lilypond@{...@}} does not generate an
452 in-line image. It always gets a paragraph of its own.
461 Music is entered using
464 <lilypond fragment relative=2>
465 \key c \minor c4 es g2
469 @command{lilypond-book} then produces an HTML file with appropriate image
470 tags for the music fragments:
472 @lilypond[fragment,relative=2]
473 \key c \minor c4 es g2
476 For inline pictures, use @code{<lilypond ... />}, where the options
477 are separated by a colon from the music, for example
480 Some music in <lilypond relative=2: a b c/> a line of text.
484 To include separate files, say
487 <lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
490 Additionally, @code{<lilypondversion/>} displays the current version
494 @cindex titling in HTML
495 @cindex preview image
500 @translationof DocBook
504 For inserting LilyPond snippets it is good to keep the conformity of our
505 DocBook document, thus allowing us to use DocBook editors, validation
506 etc. So we don't use custom tags, only specify a convention based on the
507 standard DocBook elements.
509 @subheading Common conventions
511 For inserting all type of snippets we use the @code{mediaobject} and
512 @code{inlinemediaobject} element, so our snippets can be formatted
513 inline or not inline. The snippet formatting options are always
514 provided in the @code{role} property of the innermost element (see in
515 next sections). Tags are chosen to allow DocBook editors format the
516 content gracefully. The DocBook files to be processed with
517 @command{lilypond-book} should have the extension @file{.lyxml}.
519 @subheading Including a LilyPond file
521 This is the most simple case. We must use the @file{.ly} extension for
522 the included file, and insert it as a standard @code{imageobject}, with
523 the following structure:
528 <imagedata fileref="music1.ly" role="printfilename" />
533 Note that you can use @code{mediaobject} or @code{inlinemediaobject}
534 as the outermost element as you wish.
536 @subheading Including LilyPond code
538 Including LilyPond code is possible by using a @code{programlisting},
539 where the language is set to @code{lilypond} with the following
545 <programlisting language="lilypond" role="fragment verbatim staffsize=16 ragged-right relative=2">
546 \context Staff \with @{
547 \remove Time_signature_engraver
548 \remove Clef_engraver@}
555 As you can see, the outermost element is a @code{mediaobject} or
556 @code{inlinemediaobject}, and there is a @code{textobject} containing
557 the @code{programlisting} inside.
559 @subheading Processing the DocBook document
561 Running @command{lilypond-book} on our @file{.lyxml} file will create a
562 valid DocBook document to be further processed with @file{.xml}
563 extension. If you use
564 @uref{http://@/dblatex@/.sourceforge@/.net@/,dblatex}, it will create a
565 PDF file from this document automatically. For HTML (HTML Help,
566 JavaHelp etc.) generation you can use the official DocBook XSL
567 stylesheets, however, it is possible that you have to make some
568 customization for it.
571 @node Music fragment options
572 @section Music fragment options
573 @translationof Music fragment options
577 In the following, a @q{LilyPond command} refers to any command described
578 in the previous sections which is handled by @command{lilypond-book} to
579 produce a music snippet. For simplicity, LilyPond commands are only
580 shown in @LaTeX{} syntax.
582 Note that the option string is parsed from left to right; if an option
583 occurs multiple times, the last one is taken.
585 The following options are available for LilyPond commands:
588 @item staffsize=@var{ht}
589 Set staff size to @var{ht}, which is measured in points.
592 Produce ragged-right lines with natural spacing, i.e.,
593 @code{ragged-right = ##t} is added to the LilyPond snippet. This is the
594 default for the @code{\lilypond@{@}} command if no @code{line-width}
595 option is present. It is also the default for the @code{lilypond}
596 environment if the @code{fragment} option is set, and no line width is
597 explicitly specified.
600 For single-line snippets, allow the staff length to be stretched to
601 equal that of the line width, i.e., @code{ragged-right = ##f} is
602 added to the LilyPond snippet.
605 @itemx line-width=@var{size}\@var{unit}
606 Set line width to @var{size}, using @var{unit} as units. @var{unit} is
607 one of the following strings: @code{cm}, @code{mm}, @code{in}, or
608 @code{pt}. This option affects LilyPond output (this is, the staff
609 length of the music snippet), not the text layout.
611 If used without an argument, set line width to a default value (as
612 computed with a heuristic algorithm).
614 If no @code{line-width} option is given, @command{lilypond-book} tries to
615 guess a default for @code{lilypond} environments which don't use the
616 @code{ragged-right} option.
619 Do not print the time signature, and turns off the timing (time signature,
620 bar lines) in the score.
623 Make @command{lilypond-book} add some boilerplate code so that you can
631 without @code{\layout}, @code{\score}, etc.
634 Do not add additional code to complete LilyPond code in music snippets.
635 Since this is the default, @code{nofragment} is redundant normally.
637 @item indent=@var{size}\@var{unit}
638 Set indentation of the first music system to @var{size}, using
639 @var{unit} as units. @var{unit} is one of the following strings:
640 @code{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
641 LilyPond, not the text layout.
644 Set indentation of the first music system to zero. This option affects
645 LilyPond, not the text layout. Since no indentation is the default,
646 @code{noindent} is redundant normally.
649 Reduce line length of a music snippet by @math{2*0.4}@dmn{in} and put
650 the output into a quotation block. The value @q{0.4@dmn{in}} can be
651 controlled with the @code{exampleindent} option.
654 Set the amount by which the @code{quote} option indents a music snippet.
657 @itemx relative=@var{n}
658 Use relative octave mode. By default, notes are specified relative to
659 middle@tie{}C. The optional integer argument specifies the octave of
660 the starting note, where the default @code{1} is middle C.
661 @code{relative} option only works when @code{fragment} option is set,
662 so @code{fragment} is automatically implied by @code{relative},
663 regardless of the presence of any @code{(no)fragment} option in the
667 LilyPond also uses @command{lilypond-book} to produce its own
668 documentation. To do that, some more obscure music fragment options are
673 The argument of a LilyPond command is copied to the output file and
674 enclosed in a verbatim block, followed by any text given with the
675 @code{intertext} option (not implemented yet); then the actual music is
676 displayed. This option does not work well with @code{\lilypond@{@}} if
677 it is part of a paragraph.
679 If @code{verbatim} is used in a @code{lilypondfile} command, it is
680 possible to enclose verbatim only a part of the source file. If the
681 source file contain a comment containing @samp{begin verbatim} (without
682 quotes), quoting the source in the verbatim block will start after the
683 last occurrence of such a comment; similarly, quoting the source verbatim
684 will stop just before the first occurrence of a comment containing
685 @samp{end verbatim}, if there is any. In the following source file
686 example, the music will be interpreted in relative mode, but the
687 verbatim quote will not show the @code{relative} block, i.e.
690 \relative c' @{ % begin verbatim
697 will be printed with a verbatim block like
705 If you would like to translate comments and variable names in verbatim
706 output but not in the sources, you may set the environment variable
707 @code{LYDOC_LOCALEDIR} to a directory path; the directory should
708 contain a tree of @file{.mo} message catalogs with @code{lilypond-doc}
712 (Only for Texinfo output.) Prepend line @code{\version
713 @@w@{"@@version@{@}"@}} to @code{verbatim} output.
716 (Only for Texinfo output.) If @command{lilypond} is called with the
717 @option{--header=@/texidoc} option, and the file to be processed is
718 called @file{foo.ly}, it creates a file @file{foo.texidoc} if there
719 is a @code{texidoc} field in the @code{\header}. The @code{texidoc}
720 option makes @command{lilypond-book} include such files, adding its
721 contents as a documentation block right before the music snippet.
723 Assuming the file @file{foo.ly} contains
727 texidoc = "This file demonstrates a single note."
733 and we have this in our Texinfo document @file{test.texinfo}
736 @@lilypondfile[texidoc]@{foo.ly@}
740 the following command line gives the expected result
743 lilypond-book --pdf --process="lilypond \
744 -dbackend=eps --header=texidoc" test.texinfo
747 Most LilyPond test documents (in the @file{input} directory of the
748 distribution) are small @file{.ly} files which look exactly like this.
750 For localization purpose, if the Texinfo document contains
751 @code{@@documentlanguage @var{LANG}} and @file{foo.ly} header
752 contains a @code{texidoc@var{LANG}} field, and if @command{lilypond}
753 is called with @option{--header=@/texidoc@var{LANG}}, then
754 @file{foo.texidoc@var{LANG}} will be included instead of
758 (Only for Texinfo output.) This option works similarly to
759 @code{texidoc} option: if @command{lilypond} is called with the
760 @option{--header=@/doctitle} option, and the file to be processed is
761 called @file{foo.ly} and contains a @code{doctitle} field in the
762 @code{\header}, it creates a file @file{foo.doctitle}. When
763 @code{doctitle} option is used, the contents of @file{foo.doctitle},
764 which should be a single line of @var{text}, is inserted in the
765 Texinfo document as @code{@@lydoctitle @var{text}}.
766 @code{@@lydoctitle} should be a macro defined in the Texinfo document.
767 The same remark about @code{texidoc} processing with localized
768 languages also applies to @code{doctitle}.
771 (Only for Texinfo output.) Do not translate comments and variable
772 names in the snippet quoted verbatim.
775 If a LilyPond input file is included with @code{\lilypondfile}, print
776 the file name right before the music snippet. For HTML output, this
777 is a link. Only the base name of the file is printed, i.e. the
778 directory part of the file path is stripped.
783 @node Invoking lilypond-book
784 @section Invoking @command{lilypond-book}
785 @translationof Invoking lilypond-book
789 @command{lilypond-book} produces a file with one of the following
790 extensions: @file{.tex}, @file{.texi}, @file{.html} or @file{.xml},
791 depending on the output format. All of @file{.tex}, @file{.texi} and
792 @file{.xml} files need further processing.
794 @subheading Format-specific instructions
796 @subsubheading @LaTeX{}
798 There are two ways of processing your @LaTeX{} document for printing or
799 publishing: getting a PDF file directly with PDF@LaTeX{}, or getting a
800 PostScript file with @LaTeX{} via a DVI to PostScript translator like
801 @command{dvips}. The first way is simpler and recommended@footnote{Note
802 that PDF@LaTeX{} and @LaTeX{} may not be both usable to compile any
803 @LaTeX{} document, that is why we explain the two ways.}, and whichever
804 way you use, you can easily convert between PostScript and PDF with
805 tools, like @command{ps2pdf} and @command{pdf2ps} included in
808 To produce a PDF file through PDF@LaTeX{}, use
811 lilypond-book --pdf yourfile.pdftex
812 pdflatex yourfile.tex
815 @cindex outline fonts
818 @cindex invoking dvips
819 To produce PDF output via @LaTeX{}/@command{dvips}/@command{ps2pdf}, you
823 lilypond-book yourfile.lytex
825 dvips -Ppdf yourfile.dvi
830 The @file{.dvi} file created by this process will not contain
831 note heads. This is normal; if you follow the instructions, they
832 will be included in the @file{.ps} and @file{.pdf} files.
834 Running @command{dvips} may produce some warnings about fonts; these
835 are harmless and may be ignored. If you are running @command{latex} in
836 twocolumn mode, remember to add @code{-t landscape} to the
837 @command{dvips} options.
839 @subsubheading Texinfo
841 To produce a Texinfo document (in any output format), follow the normal
842 procedures for Texinfo; this is, either call @command{texi2pdf} or
843 @command{texi2dvi} or @command{makeinfo}, depending on the output format
846 @xref{Format with texi2dvi, , , texinfo, GNU Texinfo}, and @ref{Creating an Info File, , , texinfo, GNU Texinfo}.
849 See the documentation of Texinfo for further details.
853 @subheading Command line options
855 @command{lilypond-book} accepts the following command line options:
858 @item -f @var{format}
859 @itemx --format=@var{format}
860 Specify the document type to process: @code{html}, @code{latex},
861 @code{texi} (the default) or @code{docbook}. If this option is missing,
862 @command{lilypond-book} tries to detect the format automatically, see
863 @ref{Filename extensions}. Currently, @code{texi} is the same as
866 @c This complicated detail is not implemented, comment it out -jm
868 The @code{texi} document type produces a Texinfo file with music
869 fragments in the printed output only. For getting images in the HTML
870 version, the format @code{texi-html} must be used instead.
873 @item -F @var{filter}
874 @itemx --filter=@var{filter}
875 Pipe snippets through @var{filter}. @code{lilypond-book} will
876 not --filter and --process at the same time. For example,
879 lilypond-book --filter='convert-ly --from=2.0.0 -' my-book.tely
884 Print a short help message.
887 @itemx --include=@var{dir}
888 Add @var{dir} to the include path. @command{lilypond-book} also looks
889 for already compiled snippets in the include path, and does not write
890 them back to the output directory, so in some cases it is necessary to
891 invoke further processing commands such as @command{makeinfo} or
892 @command{latex} with the same @code{-I @var{dir}} options.
895 @itemx --output=@var{dir}
896 Place generated files in directory @var{dir}. Running
897 @command{lilypond-book} generates lots of small files that LilyPond will
898 process. To avoid all that garbage in the source directory, use the
899 @option{--output} command line option, and change to that directory
900 before running @command{latex} or @command{makeinfo}.
903 lilypond-book --output=out yourfile.lytex
908 @itemx --skip-lily-check
909 Do not fail if no lilypond output is found. It is used for LilyPond
910 Info documentation without images.
912 @itemx --skip-png-check
913 Do not fail if no PNG images are found for EPS files. It is used for
914 LilyPond Info documentation without images.
916 @itemx --lily-output-dir=@var{dir}
917 Write lily-XXX files to directory @var{dir}, link into @code{--output}
918 directory. Use this option to save building time for documents in
919 different directories which share a lot of identical snippets.
921 @itemx --info-images-dir=@var{dir}
922 Format Texinfo output so that Info will look for images of music in
925 @itemx --latex-program=@var{prog}
926 Run executable @command{prog} instead of @command{latex}. This is
927 useful if your document is processed with @command{xelatex}, for
930 @itemx --left-padding=@var{amount}
931 Pad EPS boxes by this much. @var{amount} is measured in millimeters,
932 and is 3.0 by default. This option should be used if the lines of
933 music stick out of the right margin.
935 The width of a tightly clipped system can vary, due to notation
936 elements that stick into the left margin, such as bar numbers and
937 instrument names. This option will shorten each line and move each
938 line to the right by the same amount.
941 @item -P @var{command}
942 @itemx --process=@var{command}
943 Process LilyPond snippets using @var{command}. The default command is
944 @code{lilypond}. @code{lilypond-book} will not @code{--filter} and
945 @code{--process} at the same time.
948 Create PDF files for use with PDF@LaTeX{}.
956 Print version information.
961 The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
962 @LaTeX{} commands that change margins and line widths after the preamble
965 Only the first @code{\score} of a LilyPond block is processed.
968 @node Filename extensions
969 @section Filename extensions
970 @translationof Filename extensions
974 You can use any filename extension for the input file, but if you do not
975 use the recommended extension for a particular format you may need to
976 manually specify the output format; for details, see @ref{Invoking lilypond-book}. Otherwise, @command{lilypond-book} automatically
977 selects the output format based on the input filename's extension.
980 @multitable @columnfractions .2 .5
981 @item @strong{extension} @tab @strong{output format}
983 @item @file{.html} @tab HTML
984 @item @file{.itely} @tab Texinfo
985 @item @file{.latex} @tab @LaTeX{}
986 @item @file{.lytex} @tab @LaTeX{}
987 @item @file{.lyxml} @tab DocBook
988 @item @file{.tely} @tab Texinfo
989 @item @file{.tex} @tab @LaTeX{}
990 @item @file{.texi} @tab Texinfo
991 @item @file{.texinfo} @tab Texinfo
992 @item @file{.xml} @tab HTML
996 If you use the same filename extension for the input file than the
997 extension @command{lilypond-book} uses for the output file, and if the
998 input file is in the same directory as @command{lilypond-book} working
999 directory, you must use @code{--output} option to make
1000 @command{lilypond-book} running, otherwise it will exit with an error
1001 message like @qq{Output would overwrite input file}.
1004 @node Alternate methods of mixing text and music
1005 @section Alternative methods of mixing text and music
1006 @translationof Alternate methods of mixing text and music
1010 This section shows methods to integrate text and music, different than
1011 the automated method with @command{lilypond-book}.
1014 * Many quotes from a large score::
1015 * Inserting LilyPond output into OpenOffice.org::
1016 * Inserting LilyPond output into other programs::
1019 @node Many quotes from a large score
1020 @unnumberedsubsec Many quotes from a large score
1021 @translationof Many quotes from a large score
1025 If you need to quote many fragments from a large score, you can also use
1026 the clip systems feature, see @ruser{Extracting fragments of music}.
1029 @node Inserting LilyPond output into OpenOffice.org
1030 @unnumberedsubsec Inserting LilyPond output into OpenOffice.org
1031 @translationof Inserting LilyPond output into OpenOffice.org
1035 @cindex OpenOffice.org
1037 LilyPond notation can be added to OpenOffice.org with
1038 @uref{http://@/ooolilypond@/.sourceforge@/.net@/,OOoLilyPond}.
1041 @node Inserting LilyPond output into other programs
1042 @unnumberedsubsec Inserting LilyPond output into other programs
1043 @translationof Inserting LilyPond output into other programs
1047 To insert LilyPond output in other programs, use @code{lilypond}
1048 instead of @code{lilypond-book}. Each example must be created
1049 individually and added to the document; consult the documentation for
1050 that program. Most programs will be able to insert LilyPond output in
1051 @file{PNG}, @file{EPS}, or @file{PDF} formats.
1053 To reduce the white space around your LilyPond score, use
1054 the following options
1062 bookTitleMarkup = ##f
1063 scoreTitleMarkup = ##f
1069 To produce a useful @file{EPS} file, use
1072 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts myfile.ly
1075 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly