1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
14 @lilypondfile[quote]{text-headword.ly}
16 This section explains how to include text (with various
17 formatting) in music scores.
20 Some text elements that are not dealt with here are discussed in other
21 specific sections: @ref{Vocal music}, @ref{Titles and headers}.
24 @cindex Text, other languages
25 @warning{To write accented and special text (such as characters
26 from other languages), simply insert the characters directly into
27 the LilyPond file. The file must be saved as UTF-8. For more
28 information, see @ref{Text encoding}.}
38 @subsection Writing text
40 This section introduces different ways of adding text to a score.
51 @subsubsection Text scripts
54 @cindex text items, non-empty
55 @cindex non-empty texts
57 It is possible to add arbitrary text indications
58 to a score, as demonstrated in the following example.
59 Such indications can also be manually placed
60 above or below the staff, using the
61 simple syntax described in @ref{Controlling direction and
64 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
65 d8^"pizz." e f g a4-"scherz." f
68 In LilyPond, such text strings are called @command{markup}
69 objects. This syntax is actually a shorthand; more complex text
70 formatting may be added to a note by explicitly using a
71 @code{\markup} block, as described in @ref{Formatting text}.
73 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
74 d8^\markup { \italic pizz. } e f g
75 a4_\markup { \tiny scherz. \bold molto } f
78 By default, text indications do not influence the note spacing.
79 However, their widths can be taken into account:
80 in the following example, the first text string does not affect
81 spacing, whereas the second one does.
83 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
84 d8^"pizz." e f g \textLengthOn a4_"scherzando" f
89 @funindex \textLengthOn
91 @funindex \textLengthOff
97 Notation Reference: @ref{Formatting text},
98 @ref{Controlling direction and placement}.
103 Internals Reference: @internalsref{TextScript}.
107 Checking to make sure that text scripts and lyrics are within the
108 margins is a relatively large computational task. To speed up
109 processing, LilyPond does not perform such calculations by
110 default; to enable it, use
113 \override Score.PaperColumn #'keep-inside-line = ##t
118 @subsubsection Text spanners
120 @cindex Text spanners
122 Some performance indications, e.g., @i{rallentando} or
123 @i{accelerando}, are written as text and are extended over many
124 measures with dotted lines.
126 Such objects, called @q{spanners}, may be created
127 from one note to another by using the following syntax:
129 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
130 \override TextSpanner #'bound-details #'left #'text = "rit."
136 The string to be printed is set through
137 object properties. By default it is printed in italic characters,
138 but different formatting can be obtained using
139 @code{\markup} blocks:
141 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
142 \override TextSpanner #'bound-details #'left #'text =
143 \markup { \upright "rit." }
148 The line style, as well as the text string, can be defined as an
149 object property. This syntax is described in @ref{Line styles}.
153 @funindex textSpannerUp
154 @code{\textSpannerUp},
155 @funindex textSpannerDown
156 @code{\textSpannerDown},
157 @funindex textSpannerNeutral
158 @code{\textSpannerNeutral}
162 Notation Reference: @ref{Line styles}.
167 Internals Reference: @internalsref{TextSpanner}.
171 @subsubsection Text marks
173 @cindex coda on bar line
174 @cindex segno on bar line
175 @cindex fermata on bar line
176 @cindex bar lines, symbols on
179 Various text elements can be added to a score using
180 the syntax described in @ref{Rehearsal marks}:
182 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
183 c4\mark "dolce" c c c
186 This syntax makes possible to put any text on a bar line;
187 more complex text formatting may be added using a @code{\markup}
188 block, as described in @ref{Formatting text}. This can be used to print
189 signs like coda, segno or fermata, by specifying the appropriate
192 @lilypond[fragment,quote,ragged-right,verbatim,relative=2]
193 c1 \mark \markup { \musicglyph #"scripts.ufermata" }
198 Such objects are only typeset above the top staff of the score; they
199 can be placed above the bar line or between notes, depending on whether
200 you specify it at the end or the middle of a bar. When specified at the
201 beginning of a score or at a line break, the mark will be printed at
202 the beginning of the line (the next line, in case of a line break).
204 @lilypond[fragment,quote,ragged-right,verbatim,relative=2]
206 c\mark "assai" \break
213 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
214 {printing-marks-at-the-end-of-a-line-or-a-score.ly}
216 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
217 {aligning-marks-with-various-notation-objects.ly}
219 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc]
220 {printing-marks-on-every-staff.ly}
224 Notation Reference: @ref{Rehearsal marks},
225 @ref{Formatting text}, @ref{The Feta font}.
230 Internals Reference: @internalsref{RehearsalMark}.
233 @c IMO this is a bug; hopefully it'll be fixed soon, so I can
234 @c delete this sentence. -gp
235 @c A workaround is suggested in the first @snippets item -vv
237 If a mark is entered at the end of the last bar of the score (where
238 there is no next line), then the mark will not be printed at
242 @subsubsection Separate text
244 @cindex separate text
245 @cindex standalone text
246 @cindex top-level text
247 @cindex text, standalone
250 A @code{\markup} block can exist by itself, outside of any
251 any @code{\score} block, as a @qq{top-level
252 expression}. This syntax is described in @ref{File structure}.
254 @lilypond[quote,ragged-right,verbatim]
256 Tomorrow, and tomorrow, and tomorrow...
261 This allows to print text separately
262 from the music, which is particularly
263 useful when the input file contains
264 several music pieces, as described in
265 @ref{Multiple scores in a book}.
267 @lilypond[quote,ragged-right,verbatim]
272 Tomorrow, and tomorrow, and tomorrow...
279 Using a specific syntax, text blocks can be spread
280 over multiple pages, making possible to print
281 text documents or books -- and therefore to
282 use LilyPond as a word processor. This syntax is described in
283 @ref{Multi-page markup}.
288 TODO: add convenient snippets in input/new -vv
293 Notation Reference: @code{Formatting text},
294 @code{File structure},
295 @ref{Multiple scores in a book},
296 @ref{Multi-page markup}.
301 Internals Reference: @internalsref{TextScript}.
307 @funindex \markuplines
311 @node Formatting text
312 @subsection Formatting text
314 This section presents basic and advanced text formatting,
315 using the @code{\markup} mode specific syntax.
318 * Text markup introduction::
319 * Common markup commands::
321 * Graphic notation inside markup::
322 * Music notation inside markup::
323 * Multi-page markup::
326 @node Text markup introduction
327 @subsubsection Text markup introduction
334 A @code{\markup} block is used to typeset text with an extensible syntax,
335 called @q{markup mode}.
336 Specific commands can be entered in this mode, using the
337 backslash @code{\} character.
338 @c TODO: move the following sentence (and add an example?) -vv
339 To @emph{print} such characters as
340 @code{\} and @code{#} in the output, use double
343 @lilypond[quote,verbatim,fragment,relative=1]
345 c1_\markup { hi there }
346 c1^\markup { hi \bold there, is \italic {anyone home?} }
347 c1_\markup { "\special {weird} #characters" }
351 An exhaustive list of @code{\markup}-specific commands can be found in
352 @ref{Text markup commands}.
355 @lilypond[quote,verbatim]
356 \header{ title = \markup{ \bold { foo \italic { bar! } } } }
359 \override Score.RehearsalMark
360 #'break-visibility = #begin-of-line-invisible
361 \override Score.RehearsalMark #'self-alignment-X = #right
363 \set Staff.instrumentName = \markup{ \column{ Alto solo } }
364 c2^\markup{ don't be \flat }
365 \override TextSpanner #'bound-details #'left #'text = \markup{\italic rit }
367 a2\mark \markup{ \large \bold Fine }
371 \addlyrics { bar, foo \markup{ \italic bar! } }
377 @cindex font switching
379 Some font switching commands are demonstrated here. Such commands
380 apply only to the first following word; several words may be affected
381 by enclosing them in braces.
384 \markup @{ \bold @{ hi there @} @}
387 @c TODO: remove the following line and example? -vv
389 For clarity, you can also do this for single arguments, e.g.,
392 \markup @{ is \italic @{ anyone @} home @}
395 The markup mode can be used to compose expressions, similar to
396 mathematical expressions, XML documents, and music expressions.
397 Such expressions can be vertically stacked, horizontally centered,
398 or aligned in different ways:
400 @lilypond[quote,verbatim,fragment,relative=1]
401 c1^\markup { \column { a bbbb \line { c d } } }
402 c1^\markup { \center-align { a bbbb c } }
403 c1^\markup { \line { a b c } }
406 Lists with no previous command are not kept distinct. In
407 the following example, the two @code{\markup} expressions
410 @c TODO: merge these two examples in a @lilypond example -vv
413 \center-align @{ @{ a b @} @{ c d @} @}
414 \center-align @{ a b c d @}
419 To keep lists of words distinct, please use quotes @code{"} or
420 the @code{\line} command
422 @lilypond[quote,verbatim,fragment,relative=1]
424 c4^\markup{ \center-align { on three lines } }
425 c4^\markup{ \center-align { "all one line" } }
426 c4^\markup{ \center-align { { on three lines } } }
427 c4^\markup{ \center-align { \line { on one line } } }
430 Markups can be stored in variables and these variables may be
431 attached to notes, like
434 allegro = \markup @{ \bold \large @{ Allegro @} @}
435 @{ a^\allegro b c d @}
438 Some objects have alignment procedures of their own, which cancel
439 out any effects of alignments applied to their markup arguments as
440 a whole. For example, the @internalsref{RehearsalMark} is
441 horizontally centered, so using @code{\mark \markup @{ \left-align
442 .. @}} has no effect.
444 In addition, vertical placement is performed after creating the
445 text markup object. If you wish to move an entire piece of
446 markup, you need to use the #'padding property or create an
447 @q{anchor} point inside the markup (generally with @code{\hspace
450 @lilypond[quote,verbatim,fragment,relative=1]
452 c'4^\markup{ \raise #5 "not raised" }
453 \once \override TextScript #'padding = #3
454 c'4^\markup{ raised }
455 c'4^\markup{ \hspace #0 \raise #1.5 raised }
458 Some situations (such as dynamic marks) have preset font-related
459 properties. If you are creating text in such situations, it is
460 advisable to cancel those properties with @code{normal-text}. See
461 @ref{Text markup commands}, for more details.
464 TODO: here are some commands that could be described here.
465 I'm putting them in bulk, prior to working on this section. -vv
477 \page-ref (see also "Table of contents")
501 This manual: @ref{Text markup commands}.
506 Internals Reference: @internalsref{TextScript}.
508 Init files: @file{scm/@/new@/-markup@/.scm}.
513 Kerning or generation of ligatures is only done when the @TeX{}
514 backend is used. In this case, LilyPond does not account for them
515 so texts will be spaced slightly too wide.
517 Syntax errors for markup mode are confusing.
519 @node Common markup commands
520 @subsubsection Common markup commands
522 Some basic formatting can be used blah blah
531 @c TODO: what's the difference between the following commands? -vv
537 Some alternate font families can easily be selected:
542 \number (only for numbers, such as fingerings and time signatures)
543 @c TODO: add \slashed-digit here? -vv
545 The size can be blah blah blah
549 Some predefined font sizes can be used blah blah
558 Some shorcuts allow to change the font size relatively to its previous value
566 Text may be printed as subscript or superscript:
571 To obtain subscripts or superscripts in a normal text size, use
575 All these settings (except the size) can be reverted to the default font:
581 @subsubsection Text alignment
588 Horizontal alignment:
599 Building a "large" markup:
612 Alignment inside a "large" markup:
622 @node Graphic notation inside markup
623 @subsubsection Graphic notation inside markup
624 Graphics around text:
631 "Standalone" graphics:
651 @node Music notation inside markup
652 @subsubsection Music notation inside markup
654 Notes can be printed in markup mode blah blah:
659 Accidental symbols can be obtained easily:
671 Some other notation objects blah blah
679 @c TODO: add \text here? -vv
681 Any musical symbol can be printed
684 @c TODO: add \lookup here? -vv
687 The markup mode has support for fret diagrams:
691 \fret-diagram-verbose
693 An entire @code{\score} block can even be nested in a @code{\markup}
694 block. In such a case, the @code{\score} must contain a @code{\layout} block.
700 @lilypond[quote,verbatim,ragged-right]
704 \relative { c4 d e f }
717 @node Multi-page markup
718 @subsubsection Multi-page markup
720 Whereas @code{\markup} is used to enter a non-breakable block of
721 text, @code{\markuplines} can be used at top-level to enter lines
722 of text that can spread over multiple pages:
727 A very long text of justified lines.
731 An other very long paragraph.
738 @code{\markuplines} accepts a list of markup, that is either the
739 result of a markup list command, or a list of markups or of markup
740 lists. The built-in markup list commands are described in
741 @ref{Text markup list commands}.
745 This manual: @ref{Text markup list commands}, @ref{New
746 markup list command definition}.
753 @funindex \markuplines
758 @c TODO: move the following subsubsec into NR3 -vv
764 * Entire document fonts::
765 * Single entry fonts::
768 @node Entire document fonts
769 @subsubsection Entire document fonts
771 It is also possible to change the default font family for the
772 entire document. This is done by calling the
773 @code{make-pango-font-tree} from within the @code{\paper} block.
774 The function takes names for the font families to use for roman,
775 sans serif and monospaced text. For example,
777 @cindex font families, setting
786 (make-pango-font-tree "Times New Roman"
793 c'^\markup { roman: foo \sans bla \typewriter bar }
797 @c we don't do Helvetica / Courier, since GS incorrectly loads
801 @node Single entry fonts
802 @subsubsection Single entry fonts
804 @cindex font selection
805 @cindex font magnification
806 @funindex font-interface
808 By setting the object properties described below, you can select a
809 font from the preconfigured font families. LilyPond has default
810 support for the feta music fonts. Text fonts are selected through
811 Pango/FontConfig. The serif font defaults to New Century
812 Schoolbook, the sans and typewriter to whatever the Pango
813 installation defaults to.
817 @item @code{font-encoding}
818 is a symbol that sets layout of the glyphs. This should only be
819 set to select different types of non-text fonts, e.g.
821 @code{fetaBraces} for piano staff braces, @code{fetaMusic} the
822 standard music font, including ancient glyphs, @code{fetaDynamic}
823 for dynamic signs and @code{fetaNumber} for the number font.
825 @item @code{font-family}
826 is a symbol indicating the general class of the typeface.
827 Supported are @code{roman} (Computer Modern), @code{sans}, and
830 @item @code{font-shape}
831 is a symbol indicating the shape of the font. There are typically
832 several font shapes available for each font family. Choices are
833 @code{italic}, @code{caps}, and @code{upright}.
835 @item @code{font-series}
836 is a symbol indicating the series of the font. There are
837 typically several font series for each font family and shape.
838 Choices are @code{medium} and @code{bold}.
842 Fonts selected in the way sketched above come from a predefined
843 style sheet. If you want to use a font from outside the style
844 sheet, then set the @code{font-name} property,
846 @lilypond[fragment,verbatim]
848 \override Staff.TimeSignature #'font-name = #"Charter"
849 \override Staff.TimeSignature #'font-size = #2
852 \override #'(font-name . "Vera Bold")
853 { This text is in Vera Bold }
859 Any font can be used, as long as it is available to
860 Pango/FontConfig. To get a full list of all available fonts, run
864 lilypond -dshow-available-fonts blabla
867 (the last argument of the command can be anything, but has to be
871 The size of the font may be set with the @code{font-size}
872 property. The resulting size is taken relative to the
873 @code{text-font-size} as defined in the @code{\paper} block.
876 @cindex font magnification