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
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 @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@{ YOUR LILYPOND CODE @}
208 Running @command{lilypond-book} yields a file that can be further
209 processed with @LaTeX{}.
211 We show some examples here. The @code{lilypond} environment
214 \begin[quote,fragment,staffsize=26]@{lilypond@}
222 @lilypond[quote,fragment,staffsize=26]
229 \lilypond[quote,fragment,staffsize=11]@{<c' e' g'>@}
235 @lilypond[quote,fragment,staffsize=11]{<c' e' g'>}
238 Currently, you cannot include @code{@{} or @code{@}} within
239 @code{\lilypond@{@}}, so this command is only useful with the
240 @code{fragment} option.
242 The default line width of the music will be adjusted by examining the
243 commands in the document preamble, the part of the document before
244 @code{\begin@{document@}}. The @command{lilypond-book} command sends
245 these to @LaTeX{} to find out how wide the text is. The line width for
246 the music fragments is then adjusted to the text width. Note that this
247 heuristic algorithm can fail easily; in such cases it is necessary to
248 use the @code{line-width} music fragment option.
250 @cindex titling and lilypond-book
251 @cindex \header in @LaTeX{} documents
253 Each snippet will call the following macros if they have been defined by
257 @item @code{\preLilyPondExample} called before the music,
259 @item @code{\postLilyPondExample} called after the music,
261 @item @code{\betweenLilyPondSystem[1]} is called between systems if
262 @code{lilypond-book} has split the snippet into several PostScript
263 files. It must be defined as taking one parameter and will be
264 passed the number of files already included in this snippet.
265 The default is to simply insert a @code{\linebreak}.
271 @cindex Latex, feta symbols
274 To include feta symbols (such as flat, segno, etc) in a LaTeX
275 document, use @code{\input@{titledefs@}}
278 \documentclass[a4paper]@{article@}
289 The font symbol names are defined in the file feta20.tex; to find
290 the location of this file, use the command
300 Sometimes it is useful to display music elements (such as ties and slurs)
301 as if they continued after the end of the fragment. This can be done by
302 breaking the staff and suppressing inclusion of the rest of the LilyPond
305 In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that
306 inclusion of other systems is terminated once the required number of
307 systems are included. Since @code{\betweenLilypondSystem} is first
308 called @emph{after} the first system, including only the first system
312 \def\betweenLilyPondSystem#1@{\endinput@}
314 \begin[fragment]@{lilypond@}
315 c'1\( e'( c'~ \break c' d) e f\)
319 If a greater number of systems is requested, a @TeX{} conditional must
320 be used before the @code{\endinput}. In this example, replace @q{2} by
321 the number of systems you want in the output,
324 \def\betweenLilyPondSystem#1@{
325 \ifnum##1<2\else\endinput\fi
329 Remember that the definition of @code{\betweenLilyPondSystem} is
330 effective until @TeX{} quits the current group (such as the @LaTeX{}
331 environment) or is overridden by another definition (which is, in
332 most cases, for the rest of the document). To reset your
336 \let\betweenLilyPondSystem\undefined
340 in your @LaTeX{} source.
342 This may be simplified by defining a @TeX{} macro
345 \def\onlyFirstNSystems#1@{
346 \def\betweenLilyPondSystem##1@{\ifnum##1<#1\else\endinput\fi@}
351 and then saying only how many systems you want before each fragment,
354 \onlyFirstNSystems@{3@}
355 \begin@{lilypond@}...\end@{lilypond@}
356 \onlyFirstNSystems@{1@}
357 \begin@{lilypond@}...\end@{lilypond@}
361 There are specific @command{lilypond-book} command line options and
362 other details to know when processing @LaTeX{} documents, see
363 @ref{Invoking lilypond-book}.
369 Texinfo is the standard format for documentation of the GNU project. An
370 example of a Texinfo document is this manual. The HTML, PDF, and Info
371 versions of the manual are made from the Texinfo document.
373 In the input file, music is specified with
376 @@lilypond[options,go,here]
385 @@lilypond[options,go,here]@{ YOUR LILYPOND CODE @}
392 @@lilypondfile[options,go,here]@{@var{filename}@}
395 When @command{lilypond-book} is run on it, this results in a Texinfo
396 file (with extension @file{.texi}) containing @code{@@image} tags for
397 HTML, Info and printed output. @command{lilypond-book} generates images
398 of the music in EPS and PDF formats for use in the printed output, and
399 in PNG format for use in HTML and Info output.
401 We show two simple examples here. A @code{lilypond} environment
419 @@lilypond[fragment,staffsize=11]@{<c' e' g'>@}
425 @lilypond[fragment,staffsize=11]{<c' e' g'>}
427 Contrary to @LaTeX{}, @code{@@lilypond@{...@}} does not generate an
428 in-line image. It always gets a paragraph of its own.
434 Music is entered using
437 <lilypond fragment relative=2>
438 \key c \minor c4 es g2
443 @command{lilypond-book} then produces an HTML file with appropriate image
444 tags for the music fragments:
446 @lilypond[fragment,relative=2]
447 \key c \minor c4 es g2
450 For inline pictures, use @code{<lilypond ... />}, where the options
451 are separated by a colon from the music, for example
454 Some music in <lilypond relative=2: a b c/> a line of text.
457 To include separate files, say
460 <lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
463 @cindex titling in HTML
464 @cindex preview image
470 For inserting LilyPond snippets it is good to keep the conformity of our
471 DocBook document, thus allowing us to use DocBook editors, validation
472 etc. So we don't use custom tags, only specify a convention based on the
473 standard DocBook elements.
475 @subheading Common conventions
477 For inserting all type of snippets we use the @code{mediaobject} and
478 @code{inlinemediaobject} element, so our snippets can be formatted
479 inline or not inline. The snippet formatting options are always
480 provided in the @code{role} property of the innermost element (see in
481 next sections). Tags are chosen to allow DocBook editors format the
482 content gracefully. The DocBook files to be processed with
483 @command{lilypond-book} should have the extension @file{.lyxml}.
485 @subheading Including a LilyPond file
487 This is the most simple case. We must use the @file{.ly} extension for
488 the included file, and insert it as a standard @code{imageobject}, with
489 the following structure:
494 <imagedata fileref="music1.ly" role="printfilename" />
499 Note that you can use @code{mediaobject} or @code{inlinemediaobject}
500 as the outermost element as you wish.
502 @subheading Including LilyPond code
504 Including LilyPond code is possible by using a @code{programlisting},
505 where the language is set to @code{lilypond} with the following
511 <programlisting language="lilypond" role="fragment verbatim staffsize=16 ragged-right relative=2">
512 \context Staff \with @{
513 \remove Time_signature_engraver
514 \remove Clef_engraver@}
521 As you can see, the outermost element is a @code{mediaobject} or
522 @code{inlinemediaobject}, and there is a @code{textobject} containing
523 the @code{programlisting} inside.
525 @subheading Processing the DocBook document
527 Running @command{lilypond-book} on our @file{.lyxml} file will create a
528 valid DocBook document to be further processed with @file{.xml}
529 extension. If you use
530 @uref{http://@/dblatex@/.sourceforge@/.net@/,dblatex}, it will create a
531 PDF file from this document automatically. For HTML (HTML Help,
532 JavaHelp etc.) generation you can use the official DocBook XSL
533 stylesheets, however, it is possible that you have to make some
534 customization for it.
537 @node Music fragment options
538 @section Music fragment options
540 In the following, a @q{LilyPond command} refers to any command described
541 in the previous sections which is handled by @command{lilypond-book} to
542 produce a music snippet. For simplicity, LilyPond commands are only
543 shown in @LaTeX{} syntax.
545 Note that the option string is parsed from left to right; if an option
546 occurs multiple times, the last one is taken.
548 The following options are available for LilyPond commands:
551 @item staffsize=@var{ht}
552 Set staff size to @var{ht}, which is measured in points.
555 Produce ragged-right lines with natural spacing, i.e.,
556 @code{ragged-right = ##t} is added to the LilyPond snippet. This is the
557 default for the @code{\lilypond@{@}} command if no @code{line-width}
558 option is present. It is also the default for the @code{lilypond}
559 environment if the @code{fragment} option is set, and no line width is
560 explicitly specified.
563 For single-line snippets, allow the staff length to be stretched to
564 equal that of the line width, i.e., @code{ragged-right = ##f} is
565 added to the LilyPond snippet.
567 @c does this option still exist in lilypond? -jm
569 Produce lines with packed spacing, i.e., @code{packed = ##t} is added
570 to the LilyPond snippet.
573 @itemx line-width=@var{size}\@var{unit}
574 Set line width to @var{size}, using @var{unit} as units. @var{unit} is
575 one of the following strings: @code{cm}, @code{mm}, @code{in}, or
576 @code{pt}. This option affects LilyPond output (this is, the staff
577 length of the music snippet), not the text layout.
579 If used without an argument, set line width to a default value (as
580 computed with a heuristic algorithm).
582 If no @code{line-width} option is given, @command{lilypond-book} tries to
583 guess a default for @code{lilypond} environments which don't use the
584 @code{ragged-right} option.
587 Do not print the time signature, and turns off the timing (time signature,
588 bar lines) in the score.
591 Make @command{lilypond-book} add some boilerplate code so that you can
599 without @code{\layout}, @code{\score}, etc.
602 Do not add additional code to complete LilyPond code in music snippets.
603 Since this is the default, @code{nofragment} is redundant normally.
605 @item indent=@var{size}\@var{unit}
606 Set indentation of the first music system to @var{size}, using
607 @var{unit} as units. @var{unit} is one of the following strings:
608 @code{cm}, @code{mm}, @code{in}, or @code{pt}. This option affects
609 LilyPond, not the text layout.
612 Set indentation of the first music system to zero. This option affects
613 LilyPond, not the text layout. Since no indentation is the default,
614 @code{noindent} is redundant normally.
617 Reduce line length of a music snippet by @math{2*0.4}@dmn{in} and put
618 the output into a quotation block. The value @q{0.4@dmn{in}} can be
619 controlled with the @code{exampleindent} option.
622 Set the amount by which the @code{quote} option indents a music snippet.
625 @itemx relative=@var{n}
626 Use relative octave mode. By default, notes are specified relative to
627 middle@tie{}C. The optional integer argument specifies the octave of
628 the starting note, where the default @code{1} is middle C.
629 @code{relative} option only works when @code{fragment} option is set,
630 so @code{fragment} is automatically implied by @code{relative},
631 regardless of the presence of any @code{(no)fragment} option in the
635 LilyPond also uses @command{lilypond-book} to produce its own
636 documentation. To do that, some more obscure music fragment options are
641 The argument of a LilyPond command is copied to the output file and
642 enclosed in a verbatim block, followed by any text given with the
643 @code{intertext} option (not implemented yet); then the actual music is
644 displayed. This option does not work well with @code{\lilypond@{@}} if
645 it is part of a paragraph.
647 If @code{verbatim} is used in a @code{lilypondfile} command, it is
648 possible to enclose verbatim only a part of the source file. If the
649 source file contain a comment containing @samp{begin verbatim} (without
650 quotes), quoting the source in the verbatim block will start after the
651 last occurrence of such a comment; similarly, quoting the source verbatim
652 will stop just before the first occurrence of a comment containing
653 @samp{end verbatim}, it there is any. In the following source file
654 example, the music will be interpreted in relative mode, but the
655 verbatim quote will not show the @code{relative} block, i.e.
658 \relative c' @{ % begin verbatim
665 will be printed with a verbatim block like
673 (Only for Texinfo output.) Prepend line @code{\version
674 @@w@{"@@version@{@}"@}} to @code{verbatim} output.
677 (Only for Texinfo output.) If @command{lilypond} is called with the
678 @option{--header=@/texidoc} option, and the file to be processed is
679 called @file{foo@/.ly}, it creates a file @file{foo@/.texidoc} if there
680 is a @code{texidoc} field in the @code{\header}. The @code{texidoc}
681 option makes @command{lilypond-book} include such files, adding its
682 contents as a documentation block right before the music snippet.
684 Assuming the file @file{foo@/.ly} contains
688 texidoc = "This file demonstrates a single note."
694 and we have this in our Texinfo document @file{test.texinfo}
697 @@lilypondfile[texidoc]@{foo.ly@}
701 the following command line gives the expected result
704 lilypond-book --process="lilypond --format=tex --tex \
705 --header=texidoc test.texinfo
708 Most LilyPond test documents (in the @file{input} directory of the
709 distribution) are small @file{.ly} files which look exactly like this.
711 For localization purpose, if the Texinfo document contains
712 @code{@@documentlanguage @var{LANG}} and @file{foo@/.ly} header
713 contains a @code{texidoc@var{LANG}} field, and if @command{lilypond}
714 is called with @option{--header=@/texidoc@var{LANG}}, then
715 @file{foo@/.texidoc@var{LANG}} will be included instead of
716 @file{foo@/.texidoc}.
719 (Only for Texinfo output.) This option is similar to quote, but only
720 the music snippet (and the optional verbatim block implied by
721 @code{verbatim} option) is put into a quotation block. This option is
722 useful if you want to @code{quote} the music snippet but not the
723 @code{texidoc} documentation block.
726 (Only for Texinfo output.) This option works similarly to
727 @code{texidoc} option: if @command{lilypond} is called with the
728 @option{--header=@/doctitle} option, and the file to be processed is
729 called @file{foo@/.ly} and contains a @code{doctitle} field in the
730 @code{\header}, it creates a file @file{foo@/.doctitle}. When
731 @code{doctitle} option is used, the contents of @file{foo@/.doctitle},
732 which should be a single line of @var{text}, is inserted in the
733 Texinfo document as @code{@@lydoctitle @var{text}}.
734 @code{@@lydoctitle} should be a macro defined in the Texinfo document.
735 The same remark about @code{texidoc} processing with localized
736 languages also applies to @code{doctitle}.
739 If a LilyPond input file is included with @code{\lilypondfile}, print
740 the file name right before the music snippet. For HTML output, this
741 is a link. Only the base name of the file is printed, i.e. the
742 directory part of the file path is stripped.
745 This option includes fonts in all of the generated EPS-files for this
746 snippet. This should be used if the snippet uses any font that @LaTeX{}
747 cannot find on its own.
752 @node Invoking lilypond-book
753 @section Invoking @command{lilypond-book}
755 @command{lilypond-book} produces a file with one of the following
756 extensions: @file{.tex}, @file{.texi}, @file{.html} or @file{.xml},
757 depending on the output format. All of @file{.tex}, @file{.texi} and
758 @file{.xml} files need further processing.
760 @subheading Format-specific instructions
762 @subsubheading @LaTeX{}
764 There are two ways of processing your @LaTeX{} document for printing or
765 publishing: getting a PDF file directly with PDF@LaTeX{}, or getting a
766 PostScript file with @LaTeX{} via a DVI to PostScript translator like
767 @command{dvips}. The first way is simpler and recommended@footnote{Note
768 that PDF@LaTeX{} and @LaTeX{} may not be both usable to compile any
769 @LaTeX{} document, that is why we explain the two ways.}, and whichever
770 way you use, you can easily convert between PostScript and PDF with
771 tools, like @command{ps2pdf} and @command{pdf2ps} included in
774 To produce a PDF file through PDF@LaTeX{}, use
777 lilypond-book --pdf yourfile.pdftex
778 pdflatex yourfile.tex
781 @cindex outline fonts
784 @cindex invoking dvips
785 To produce PDF output via @LaTeX{}/@command{dvips}/@command{ps2pdf}, you
789 lilypond-book yourfile.lytex
791 dvips -Ppdf yourfile.dvi
796 The @file{.dvi} file created by this process will not contain
797 note heads. This is normal; if you follow the instructions, they
798 will be included in the @file{.ps} and @file{.pdf} files.
800 Running @command{dvips} may produce some warnings about fonts; these
801 are harmless and may be ignored. If you are running @command{latex} in
802 twocolumn mode, remember to add @code{-t landscape} to the
803 @command{dvips} options.
805 @subsubheading Texinfo
807 To produce a Texinfo document (in any output format), follow the normal
808 procedures for Texinfo; this is, either call @command{texi2pdf} or
809 @command{texi2dvi} or @command{makeinfo}, depending on the output format
812 @xref{Format with texi2dvi, , , texinfo, GNU Texinfo}, and @ref{Creating
813 an Info File, , , texinfo, GNU Texinfo}.
816 See the documentation of Texinfo for further details.
820 @subheading Command line options
822 @command{lilypond-book} accepts the following command line options:
825 @item -f @var{format}
826 @itemx --format=@var{format}
827 Specify the document type to process: @code{html}, @code{latex},
828 @code{texi} (the default) or @code{docbook}. If this option is missing,
829 @command{lilypond-book} tries to detect the format automatically, see
830 @ref{Filename extensions}. Currently, @code{texi} is the same as
833 @c This complicated detail is not implemented, comment it out -jm
835 The @code{texi} document type produces a Texinfo file with music
836 fragments in the printed output only. For getting images in the HTML
837 version, the format @code{texi-html} must be used instead.
840 @item -F @var{filter}
841 @itemx --filter=@var{filter}
842 Pipe snippets through @var{filter}. @code{lilypond-book} will
843 not --filter and --process at the same time. For example,
846 lilypond-book --filter='convert-ly --from=2.0.0 -' my-book.tely
851 Print a short help message.
854 @itemx --include=@var{dir}
855 Add @var{dir} to the include path. @command{lilypond-book} also looks
856 for already compiled snippets in the include path, and does not write
857 them back to the output directory, so in some cases it is necessary to
858 invoke further processing commands such as @command{makeinfo} or
859 @command{latex} with the same @code{-I @var{dir}} options.
862 @itemx --output=@var{dir}
863 Place generated files in directory @var{dir}. Running
864 @command{lilypond-book} generates lots of small files that LilyPond will
865 process. To avoid all that garbage in the source directory, use the
866 @option{--output} command line option, and change to that directory
867 before running @command{latex} or @command{makeinfo}.
870 lilypond-book --output=out yourfile.lytex
875 @itemx --skip-lily-check
876 Do not fail if no lilypond output is found. It is used for LilyPond
877 Info documentation without images.
879 @itemx --skip-png-check
880 Do not fail if no PNG images are found for EPS files. It is used for
881 LilyPond Info documentation without images.
883 @itemx --lily-output-dir=@var{dir}
884 Write lily-XXX files to directory @var{dir}, link into @code{--output}
885 directory. Use this option to save building time for documents in
886 different directories which share a lot of identical snippets.
888 @itemx --info-images-dir=@var{dir}
889 Format Texinfo output so that Info will look for images of music in
892 @itemx --latex-program=@var{prog}
893 Run executable @command{prog} instead of @command{latex}. This is
894 useful if your document is processed with @command{xelatex}, for
897 @itemx --left-padding=@var{amount}
898 Pad EPS boxes by this much. @var{amount} is measured in millimeters,
899 and is 3.0 by default. This option should be used if the lines of
900 music stick out of the right margin.
902 The width of a tightly clipped system can vary, due to notation
903 elements that stick into the left margin, such as bar numbers and
904 instrument names. This option will shorten each line and move each
905 line to the right by the same amount.
908 @item -P @var{command}
909 @itemx --process=@var{command}
910 Process LilyPond snippets using @var{command}. The default command is
911 @code{lilypond}. @code{lilypond-book} will not @code{--filter} and
912 @code{--process} at the same time.
915 Create PDF files for use with PDF@LaTeX{}.
923 Print version information.
928 The Texinfo command @code{@@pagesizes} is not interpreted. Similarly,
929 @LaTeX{} commands that change margins and line widths after the preamble
932 Only the first @code{\score} of a LilyPond block is processed.
935 @node Filename extensions
936 @section Filename extensions
938 You can use any filename extension for the input file, but if you do not
939 use the recommended extension for a particular format you may need to
940 manually specify the output format; for details, see @ref{Invoking
941 lilypond-book}. Otherwise, @command{lilypond-book} automatically
942 selects the output format based on the input filename's extension.
945 @multitable @columnfractions .2 .5
946 @item @strong{extension} @tab @strong{output format}
948 @item @file{.html} @tab HTML
949 @item @file{.itely} @tab Texinfo
950 @item @file{.latex} @tab @LaTeX{}
951 @item @file{.lytex} @tab @LaTeX{}
952 @item @file{.lyxml} @tab DocBook
953 @item @file{.tely} @tab Texinfo
954 @item @file{.tex} @tab @LaTeX{}
955 @item @file{.texi} @tab Texinfo
956 @item @file{.texinfo} @tab Texinfo
957 @item @file{.xml} @tab HTML
961 If you use the same filename extension for the input file than the
962 extension @command{lilypond-book} uses for the output file, and if the
963 input file is in the same directory as @command{lilypond-book} working
964 directory, you must use @code{--output} option to make
965 @command{lilypond-book} running, otherwise the will exit with an error
966 message like @qq{Output would overwrite input file}.
969 @node Alternate methods of mixing text and music
970 @section Alternative methods of mixing text and music
972 This section shows methods to integrate text and music, different than
973 the automated method with @command{lilypond-book}.
976 * Many quotes from a large score::
977 * Inserting LilyPond output into OpenOffice.org::
978 * Inserting LilyPond output into other programs::
981 @node Many quotes from a large score
982 @unnumberedsubsec Many quotes from a large score
984 If you need to quote many fragments from a large score, you can also use
985 the clip systems feature, see @ruser{Extracting fragments of music}.
988 @node Inserting LilyPond output into OpenOffice.org
989 @unnumberedsubsec Inserting LilyPond output into OpenOffice.org
991 @cindex OpenOffice.org
993 LilyPond notation can be added to OpenOffice.org with
994 @uref{http://@/ooolilypond@/.sourceforge@/.net@/,OOoLilyPond}.
997 @node Inserting LilyPond output into other programs
998 @unnumberedsubsec Inserting LilyPond output into other programs
1000 To insert LilyPond output in other programs, use @code{lilypond}
1001 instead of @code{lilypond-book}. Each example must be created
1002 individually and added to the document; consult the documentation for
1003 that program. Most programs will be able to insert LilyPond output in
1004 @file{PNG}, @file{EPS}, or @file{PDF} formats.
1006 To reduce the white space around your LilyPond score, use
1007 the following options
1015 bookTitleMarkup = ##f
1016 scoreTitleMarkup = ##f
1022 To produce a useful @file{EPS} file, use
1025 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts myfile.ly
1028 lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts --png myfile.ly