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. For details, see the Contributors'
7 Guide, node Updating translation committishes..
15 @lilypondfile[quote]{text-headword.ly}
17 This section explains how to include text (with various
18 formatting) in music scores.
21 Some text elements that are not dealt with here are discussed in other
22 specific sections: @ref{Vocal music}, @ref{Titles and headers}.
31 @subsection Writing text
33 This section introduces different ways of adding text to a score.
35 @cindex Text, other languages
36 @warning{To write accented and special text (such as characters
37 from other languages), simply insert the characters directly into
38 the LilyPond file. The file must be saved as UTF-8. For more
39 information, see @ref{Text encoding}.}
50 @unnumberedsubsubsec Text scripts
53 @cindex text items, non-empty
54 @cindex non-empty texts
57 Simple @qq{quoted text} indications may be added to a score, as
58 demonstrated in the following example. Such indications may be
59 manually placed above or below the staff, using the syntax described
60 in @ref{Direction and placement}.
62 @lilypond[quote,verbatim,relative=2]
63 a8^"pizz." g f e a4-"scherz." f
66 This syntax is actually a shorthand; more complex text formatting may be
67 added to a note by explicitly using a @code{\markup} block, as described
68 in @ref{Formatting text}.
70 @lilypond[quote,verbatim,relative=2]
71 a8^\markup { \italic pizz. } g f e
72 a4_\markup { \tiny scherz. \bold molto } f
75 By default, text indications do not influence the note spacing. However,
76 their widths can be taken into account: in the following example, the
77 first text string does not affect spacing, whereas the second one does.
79 @lilypond[quote,verbatim,relative=2]
85 In addition to text scripts, articulations can be attached to notes.
86 For more information, see @ref{Articulations and ornamentations}.
88 For more information about the relative ordering of text scripts and
89 articulations, see @rlearning{Placement of objects}.
91 @funindex \textLengthOn
92 @funindex textLengthOn
93 @funindex \textLengthOff
94 @funindex textLengthOff
98 @code{\textLengthOff}.
103 @rlearning{Placement of objects}.
106 @ref{Formatting text},
107 @ref{Direction and placement},
108 @ref{Articulations and ornamentations}.
114 @rinternals{TextScript}.
116 @cindex text outside margin
117 @cindex margin, text running over
118 @cindex text, keeping inside margin
119 @cindex lyrics, keeping inside margin
122 Checking to make sure that text scripts and lyrics are within the
123 margins requires additonal calculations. In cases where slightly faster
124 performance is desired, use
127 \override Score.PaperColumn.keep-inside-line = ##f
132 @unnumberedsubsubsec Text spanners
134 @cindex text spanners
136 Some performance indications, e.g., @notation{rallentando} or
137 @notation{accelerando}, are written as text and are extended over
138 multiple notes with dotted lines. Such objects, called
139 @qq{spanners}, may be created from one note to another using the
142 @lilypond[verbatim,quote,relative=2]
143 \override TextSpanner.bound-details.left.text = "rit."
148 @cindex text spanners, formatting
149 @cindex formatting text spanners
152 The string to be printed is set through object properties. By default
153 it is printed in italic characters, but different formatting can be
154 obtained using @code{\markup} blocks, as described in
155 @ref{Formatting text}.
157 @lilypond[quote,relative=2,verbatim]
158 \override TextSpanner.bound-details.left.text =
159 \markup { \upright "rit." }
164 The line style, as well as the text string, can be defined as an
165 object property. This syntax is described in @ref{Line styles}.
167 @funindex \textSpannerUp
168 @funindex textSpannerUp
169 @funindex \textSpannerDown
170 @funindex textSpannerDown
171 @funindex \textSpannerNeutral
172 @funindex textSpannerNeutral
176 @code{\textSpannerUp},
177 @code{\textSpannerDown},
178 @code{\textSpannerNeutral}.
182 LilyPond is only able to handle one text spanner per voice.
186 @lilypondfile[verbatim,quote,texidoc,doctitle]
187 {dynamics-text-spanner-postfix.ly}
189 @lilypondfile[verbatim,quote,texidoc,doctitle]
190 {dynamics-custom-text-spanner-postfix.ly}
196 @ref{Formatting text}.
200 @rlsr{Expressive marks}.
203 @rinternals{TextSpanner}.
207 @unnumberedsubsubsec Text marks
212 @cindex text on bar line
213 @cindex coda on bar line
214 @cindex segno on bar line
215 @cindex fermata on bar line
216 @cindex bar lines, symbols on
223 Various text elements may be added to a score using the syntax described
224 in @ref{Rehearsal marks}:
226 @c \mark needs to be placed on a separate line (it's not
227 @c attached to an object like \markup is). -vv
229 @lilypond[verbatim,quote,relative=2]
235 This syntax makes it possible to put any text on a bar line;
236 more complex text formatting may be added using a @code{\markup}
237 block, as described in @ref{Formatting text}:
239 @lilypond[quote,verbatim,relative=1]
241 \mark \markup { \italic { colla parte } }
247 This syntax also allows to print special signs, like coda, segno
248 or fermata, by specifying the appropriate symbol name as explained in
249 @ref{Music notation inside markup}:
251 @lilypond[quote,verbatim,relative=2]
253 \mark \markup { \musicglyph #"scripts.ufermata" }
258 Such objects are only typeset above the top staff of the score;
259 depending on whether they are specified at the end or the middle of a
260 bar, they can be placed above the bar line or between notes. When
261 specified at a line break, the mark will be printed at the beginning of
264 @lilypond[quote,verbatim,relative=2,ragged-right]
271 @funindex \markLengthOn
272 @funindex markLengthOn
273 @funindex \markLengthOff
274 @funindex markLengthOff
277 @code{\markLengthOn},
278 @code{\markLengthOff}.
283 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
284 {printing-marks-at-the-end-of-a-line.ly}
286 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
287 {printing-marks-on-every-staff.ly}
291 @ref{Rehearsal marks},
292 @ref{Formatting text},
293 @ref{Music notation inside markup},
300 @rinternals{MarkEvent},
301 @rinternals{Mark_engraver},
302 @rinternals{RehearsalMark}.
306 @unnumberedsubsubsec Separate text
308 @cindex separate text
309 @cindex text, separate
310 @cindex standalone text
311 @cindex top-level text
312 @cindex text, top-level
313 @cindex text, standalone
318 A @code{\markup} block can exist by itself, outside of any
319 @code{\score} block, as a @qq{top-level expression}. This syntax
320 is described in @ref{File structure}.
322 @lilypond[verbatim,quote]
324 Tomorrow, and tomorrow, and tomorrow...
329 This allows printing text separately from the music, which is
330 particularly useful when the input file contains several music pieces,
331 as described in @ref{Multiple scores in a book}.
333 @lilypond[quote,verbatim]
338 Tomorrow, and tomorrow, and tomorrow...
345 Separate text blocks can be spread over multiple pages,
346 making it possible to print text documents or books entirely
347 within LilyPond. This feature, and the specific syntax it
348 requires, are described in @ref{Multi-page markup}.
353 @funindex \markuplist
364 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
365 {stand-alone-two-column-markup.ly}
369 @ref{Formatting text},
370 @ref{File structure},
371 @ref{Multiple scores in a book},
372 @ref{Multi-page markup}.
378 @rinternals{TextScript}.
381 @node Formatting text
382 @subsection Formatting text
384 This section presents basic and advanced text formatting,
385 using the @code{\markup} mode specific syntax.
388 * Text markup introduction::
389 * Selecting font and font size::
391 * Graphic notation inside markup::
392 * Music notation inside markup::
393 * Multi-page markup::
396 @node Text markup introduction
397 @unnumberedsubsubsec Text markup introduction
407 A @code{\markup} block is used to typeset text with an extensible
408 syntax called @qq{markup mode}.
410 @cindex markup expressions
411 @cindex expressions, markup
412 @cindex markup syntax
413 @cindex syntax, markup
415 The markup syntax is similar to LilyPond's usual syntax: a
416 @code{\markup} expression is enclosed in curly braces
417 @code{@{@dots{} @}}. A single word is regarded as a minimal expression,
418 and therefore does not need to be enclosed with braces.
420 Unlike simple @qq{quoted text} indications, @code{\markup} blocks may
421 contain nested expressions or markup commands, entered using the
422 backslash @code{\} character. Such commands only affect the first
423 following expression.
425 @lilypond[quote,verbatim,relative=2]
427 a2^\markup { poco \italic più forte }
429 d2_\markup { \italic "string. assai" }
431 b1^\markup { \bold { molto \italic agitato } }
435 @cindex special characters in markup mode
436 @cindex markup mode, special characters
437 @cindex reserved characters, printing
438 @cindex printing reserved characters
439 @cindex printing special characters
440 @cindex quoted text in markup mode
441 @cindex markup mode, quoted text
443 A @code{\markup} block may also contain quoted text strings. Such
444 strings are treated as minimal text expressions, and therefore any
445 markup command or special character (such as @code{\} and@tie{}@code{#})
446 will be printed verbatim without affecting the formatting of the text.
447 Double quotation marks themselves may be printed by preceding them
450 @lilypond[quote,verbatim,relative=2]
451 a1^"\italic markup..."
452 a_\markup { \italic "... prints \"italic\" letters!" }
456 To be treated as a distinct expression, a list of words needs to be
457 enclosed with double quotes or preceded by a command. The way markup
458 expressions are defined affects how these expressions will be stacked,
459 centered and aligned; in the following example, the second
460 @code{\markup} expression is treated the same as the first one:
462 @lilypond[quote,verbatim,relative=2]
463 c1^\markup { \center-column { a bbb c } }
464 c1^\markup { \center-column { a { bbb c } } }
465 c1^\markup { \center-column { a \line { bbb c } } }
466 c1^\markup { \center-column { a "bbb c" } }
469 Markups can be stored in variables. Such variables may be
470 directly attached to notes:
472 @lilypond[quote,verbatim]
473 allegro = \markup { \bold \large Allegro }
483 An exhaustive list of @code{\markup}-specific commands can be found in
484 @ref{Text markup commands}.
488 @ref{Text markup commands}.
494 @file{scm/markup.scm}.
497 Syntax errors for markup mode can be confusing.
500 @node Selecting font and font size
501 @unnumberedsubsubsec Selecting font and font size
503 @cindex font switching
504 @cindex changing fonts
505 @cindex switching fonts
514 Basic font switching is supported in markup mode:
516 @lilypond[quote,verbatim,relative=2]
519 \italic { non troppo \underline Vivo }
522 d,_\markup { \italic quasi \smallCaps Tromba }
529 @funindex \abs-fontsize
539 The font size can be altered, relative to the global staff size, in a
540 number of different ways
542 It can be set to predefined size,
544 @lilypond[quote,verbatim,relative=2]
545 b1_\markup { \huge Sinfonia }
546 b1^\markup { \teeny da }
547 b1-\markup { \normalsize camera }
550 It can be set relative to its previous value,
552 @lilypond[quote,verbatim,relative=2]
553 b1_\markup { \larger Sinfonia }
554 b1^\markup { \smaller da }
555 b1-\markup { \magnify #0.6 camera }
558 It can be increased or decreased relative to the value set by the
561 @lilypond[quote,verbatim,relative=2]
562 b1_\markup { \fontsize #-2 Sinfonia }
563 b1^\markup { \fontsize #1 da }
564 b1-\markup { \fontsize #3 camera }
567 It can also be set to a fixed point-size, regardless of the global staff
570 @lilypond[quote,verbatim,relative=2]
571 b1_\markup { \abs-fontsize #20 Sinfonia }
572 b1^\markup { \abs-fontsize #8 da }
573 b1-\markup { \abs-fontsize #14 camera }
583 @funindex \normal-size-super
584 @funindex normal-size-super
586 Text may be printed as subscript or superscript. By default these are
587 printed in a smaller size, but a normal size can be used as well:
589 @lilypond[quote,verbatim]
592 \line { 1 \super st movement }
593 \line { 1 \normal-size-super st movement
594 \sub { (part two) } }
599 @cindex font families
601 The markup mode provides an easy way to select alternate font
602 families. The default serif font, of roman type, is automatically
603 selected unless specified otherwise; on the last line of the following
604 example, there is no difference between the first and the second word.
606 @lilypond[quote,verbatim]
609 \line { Act \number 1 }
610 \line { \sans { Scene I. } }
611 \line { \typewriter { Verona. An open place. } }
612 \line { Enter \roman Valentine and Proteus. }
618 Some of these font families, used for specific items such as numbers
619 or dynamics, do not provide all characters, as mentioned in
620 @ref{New dynamic marks} and @ref{Manual repeat marks}.
622 @c \concat is actually documented in Align (it is not
623 @c a font-switching command). But we need it here. -vv
625 When used inside a word, some font-switching or formatting commands
626 may produce an unwanted blank space. This can easily be solved by
627 concatenating the text elements together:
629 @lilypond[quote,verbatim]
633 \concat { 1 \super st }
637 \concat { \dynamic p , }
638 \italic { con dolce espressione }
644 An exhaustive list of font switching commands and custom font usage
645 commands can be found in @ref{Font}.
647 Defining custom font sets is also possible, as explained in
656 @funindex \normalsize
682 @ref{New dynamic marks},
683 @ref{Manual repeat marks},
687 @file{scm/define-markup-commands.scm}.
693 @rinternals{TextScript}.
696 Using the font sizing commands @code{\teeny}, @code{\tiny},
697 @code{\small}, @code{\normalsize}, @code{\large}, and
698 @code{\huge} will lead to inconsistent line spacing compared to
699 using @code{\fontsize}.
703 @unnumberedsubsubsec Text alignment
705 @cindex text, aligning
706 @cindex aligning text
707 @cindex aligning markup text
708 @cindex aligning markups
709 @cindex markups, aligning
710 @cindex markup text, aligning
712 This subsection discusses how to place text in markup mode. Markup
713 objects can also be moved as a whole, using the syntax described in
714 @rlearning{Moving objects}.
716 @c Padding commands should be mentioned on this page, but
717 @c most of these require \box to be more clearly illustrated. -vv
719 @cindex text, horizontal alignment
720 @cindex horizontal text alignment
722 @funindex \left-align
724 @funindex \center-align
725 @funindex center-align
726 @funindex \right-align
727 @funindex right-align
729 Markup objects may be aligned in different ways. By default, a text
730 indication is aligned on its left edge: in the following example,
731 there is no difference between the first and the second markup.
733 @lilypond[quote,verbatim,relative=2]
736 d-\markup { \left-align poco }
738 d-\markup { \center-align { poco } }
740 d-\markup { \right-align poco }
746 Horizontal alignment may be fine-tuned using a numeric value:
748 @lilypond[quote,verbatim,relative=2]
749 a1-\markup { \halign #-1 poco }
751 a,-\markup { \halign #0 poco }
753 a,-\markup { \halign #0.5 poco }
755 a,-\markup { \halign #2 poco }
759 Some objects may have alignment procedures of their own, and therefore
760 are not affected by these commands. It is possible to move such
761 markup objects as a whole, as shown for instance in
764 @cindex text, vertical alignment
765 @cindex vertical text alignment
774 @c QUERY Should the function of ``\null'' be clarified? rp
776 Vertical alignment is a bit more complex. As stated above, markup
777 objects can be moved as a whole; however, it is also possible to move
778 specific elements inside a markup block. In this case, the element to
779 be moved needs to be preceded with an @emph{anchor point}, that can be
780 another markup element or an invisible object. The following example
781 demonstrates these two possibilities; the last markup in this example
782 has no anchor point, and therefore is not moved.
784 @lilypond[quote,verbatim,relative=1]
787 \raise #2 { Scène 1 }
792 \lower #4 \bold { Très modéré }
796 \raise #4 \italic { Une forêt. }
801 @funindex \general-align
802 @funindex general-align
805 @funindex \translate-scaled
806 @funindex translate-scaled
808 Some commands can affect both the horizontal and vertical alignment of
809 text objects in markup mode. Any object affected by these commands
810 must be preceded with an anchor point:
812 @lilypond[quote,verbatim,relative=1]
815 \translate #'(-1 . 2) "Scène 1"
820 \general-align #Y #3.2 \bold "Très modéré"
825 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
830 @cindex multi-line markup
831 @cindex markup, multi-line
832 @cindex multi-line text
833 @cindex text, multi-line
834 @cindex text in columns
835 @cindex columns, text
839 @funindex \center-column
840 @funindex center-column
842 A markup object may include several lines of text. In the following
843 example, each element or expression is placed on its own line, either
844 left-aligned or centered:
846 @lilypond[quote,verbatim]
862 @cindex centering text on the page
863 @cindex text, centering on the page
864 @cindex markup, centering on the page
869 Similarly, a list of elements or expressions may be spread to fill the
870 entire horizontal line width (if there is only one element, it will be
871 centered on the page). These expressions can, in turn, include
872 multi-line text or any other markup expression:
874 @lilypond[quote,verbatim]
877 \line { William S. Gilbert }
879 \huge \smallCaps "The Mikado"
881 \smallCaps "The Town of Titipu"
883 \line { Sir Arthur Sullivan }
891 @cindex wordwrapped text
892 @cindex justified text
893 @cindex text, justified
894 @cindex text, wordwrapped
895 @cindex markup text, wordwrapped
896 @cindex markup text, justified
903 Long text indications can also be automatically wrapped accordingly to
904 the given line width. These will be either left-aligned or justified,
905 as shown in the following example.
907 @lilypond[quote,verbatim]
910 \line \smallCaps { La vida breve }
911 \line \bold { Acto I }
913 (La escena representa el corral de una casa de
914 gitanos en el AlbaicÃn de Granada. Al fondo una
915 puerta por la que se ve el negro interior de
916 una Fragua, iluminado por los rojos resplandores
921 \line \bold { Acto II }
922 \override #'(line-width . 50)
924 (Calle de Granada. Fachada de la casa de Carmela
925 y su hermano Manuel con grandes ventanas abiertas
926 a través de las que se ve el patio
927 donde se celebra una alegre fiesta)
933 @cindex text alignment commands
934 @cindex markup text alignment commands
935 @cindex alignment, text, commands
937 An exhaustive list of text alignment commands can be found in
942 @rlearning{Moving objects}.
949 @file{scm/define-markup-commands.scm}.
955 @rinternals{TextScript}.
958 @node Graphic notation inside markup
959 @unnumberedsubsubsec Graphic notation inside markup
961 @cindex graphics, embedding
962 @cindex drawing graphic objects
963 @cindex graphic objects, drawing
964 @cindex embedding graphic objects
965 @cindex graphic objects, embedding
967 Various graphic objects may be added to a score, using markup
970 @cindex decorating text
972 @cindex text, framing
973 @cindex text, decorating
974 @cindex markup text, decorating
975 @cindex markup text, framing
981 @funindex \rounded-box
982 @funindex rounded-box
988 Some markup commands allow decoration of text elements with graphics,
989 as demonstrated in the following example.
991 @lilypond[quote,verbatim]
1000 \bracket "1866 - 1925"
1003 \rounded-box \bold Prelude
1008 @cindex padding around text
1009 @cindex text padding
1010 @cindex markup text padding
1012 @funindex \pad-markup
1013 @funindex pad-markup
1016 @funindex \pad-to-box
1017 @funindex pad-to-box
1018 @funindex \pad-around
1019 @funindex pad-around
1021 Some commands may require an increase in the padding around the text;
1022 this is achieved with some markup commands exhaustively described in
1025 @lilypond[quote,verbatim]
1026 \markup \fill-line {
1028 \box "Charles Ives (1874 - 1954)"
1030 \box \pad-markup #2 "THE UNANSWERED QUESTION"
1031 \box \pad-x #8 "A Cosmic Landscape"
1038 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
1039 \bold "Largo to Presto"
1042 "String quartet keeps very even time,
1043 Flute quartet keeps very uneven time."
1047 @cindex graphic notation
1048 @cindex symbols, non-musical
1049 @cindex non-musical symbols
1050 @cindex notation, graphic
1054 @funindex \draw-circle
1055 @funindex draw-circle
1056 @funindex \filled-box
1057 @funindex filled-box
1060 @funindex \draw-line
1062 @funindex \arrow-head
1063 @funindex arrow-head
1065 Other graphic elements or symbols may be printed without requiring any
1066 text. As with any markup expression, such objects can be combined.
1068 @lilypond[quote,verbatim]
1071 \draw-circle #4 #0.4 ##f
1072 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
1078 \draw-line #'(0 . 4)
1079 \arrow-head #Y #DOWN ##f
1084 @cindex embedded graphics
1085 @cindex images, embedding
1086 @cindex graphics, embedding
1091 @funindex \postscript
1092 @funindex postscript
1094 Advanced graphic features include the ability to include external
1095 image files converted to the Encapsulated PostScript format
1096 (@emph{eps}), or to directly embed graphics into the input file, using
1097 native PostScript code. In such a case, it may be useful to
1098 explicitly specify the size of the drawing, as demonstrated below:
1100 @lilypond[quote,verbatim,relative=1]
1103 \epsfile #X #10 #"./context-example.eps"
1104 \with-dimensions #'(0 . 6) #'(0 . 10)
1120 An exhaustive list of graphics-specific commands can be found in
1126 @ref{Editorial annotations},
1130 @file{scm/define-markup-commands.scm},
1131 @file{scm/stencil.scm}.
1136 Internals Reference:
1137 @rinternals{TextScript}.
1140 @node Music notation inside markup
1141 @unnumberedsubsubsec Music notation inside markup
1143 @cindex notation inside markup
1144 @cindex music inside markup
1145 @cindex markup, music notation inside
1147 Various musical notation elements may be added to a score, inside a
1150 Notes and accidentals can be entered using markup commands:
1152 @lilypond[quote,verbatim,relative=2]
1156 \note-by-number #1 #1 #1.5
1159 \natural \semiflat \flat
1160 \sesquiflat \doubleflat
1164 \natural \semisharp \sharp
1165 \sesquisharp \doublesharp
1170 Other notation objects may also be printed
1173 @lilypond[quote,verbatim,relative=1]
1175 ees\finger \markup \tied-lyric #"4~1"
1176 fis_\markup { \dynamic rf }
1187 More generally, any available musical symbol may be included
1188 separately in a markup object, as demonstrated below; an exhaustive
1189 list of these symbols and their names can be found in
1190 @ref{The Feta font}.
1192 @lilypond[quote,verbatim,relative=2]
1194 c'^\markup { \musicglyph #"eight" }
1196 c,8._\markup { \musicglyph #"clefs.G_change" }
1198 c2^\markup { \musicglyph #"timesig.neomensural94" }
1201 Another way of printing non-text glyphs is described in
1202 @ref{Fonts explained}. This is useful for printing braces of various
1205 The markup mode also supports diagrams for specific
1208 @lilypond[quote,verbatim,relative=2]
1210 \fret-diagram-terse #"x;x;o;2;3;2;"
1213 \harp-pedal #"^-v|--ov^"
1218 \musicglyph #"accordion.discant"
1220 \raise #0.5 \musicglyph #"accordion.dot"
1221 \raise #1.5 \musicglyph #"accordion.dot"
1225 @c The accordion diagram is actually taken from a snippet.
1228 Such diagrams are documented in @ref{Instrument Specific Markup}.
1230 @cindex score inside markup
1231 @cindex markup, score inside
1233 A whole score can even be nested inside a markup object. In such a
1234 case, the nested @code{\score} block must contain a @code{\layout}
1235 block, as demonstrated here:
1237 @lilypond[quote,verbatim,relative=1]
1240 \relative c' { c4 d e f }
1248 An exhaustive list of music notation related commands can be found in
1254 @ref{The Feta font},
1255 @ref{Fonts explained}.
1258 @file{scm/define-markup-commands.scm},
1259 @file{scm/fret-diagrams.scm},
1260 @file{scm/harp-pedals.scm}.
1265 Internals Reference:
1266 @rinternals{TextScript}.
1269 @node Multi-page markup
1270 @unnumberedsubsubsec Multi-page markup
1272 @cindex multi-page markup
1273 @cindex markup, multi-page
1274 @cindex markup text, multi-page
1275 @cindex text spread over multiple pages
1277 @funindex \markuplist
1278 @funindex markuplist
1279 @funindex \justified-lines
1280 @funindex justified-lines
1281 @funindex \wordwrap-lines
1282 @funindex wordwrap-lines
1284 Although standard markup objects are not breakable, a specific syntax
1285 makes it possible to enter lines of text that can spread over multiple
1288 @lilypond[quote,verbatim]
1291 A very long text of justified lines.
1295 Another very long paragraph.
1302 This syntax accepts a list of markups, that can be
1305 the result of a markup list command,
1309 a list of markup lists.
1312 An exhaustive list of markup list commands can be found in
1313 @ref{Text markup list commands}.
1317 @ref{Text markup list commands}.
1320 @rextend{New markup list command definition}.
1323 @file{scm/define-markup-commands.scm}.
1328 Internals Reference:
1329 @rinternals{TextScript}.
1331 @funindex \markuplist
1332 @funindex markuplist
1342 This section presents the way fonts are handled, and how they may be
1347 * Single entry fonts::
1348 * Entire document fonts::
1351 @node Fonts explained
1352 @unnumberedsubsubsec Fonts explained
1355 @cindex fonts, explained
1356 @cindex braces, various sizes
1357 @cindex fonts, non-text in markup
1358 @cindex non-text fonts in markup
1360 @funindex font-interface
1362 Fonts are handled through several libraries. FontConfig is used to
1363 detect available fonts on the system; the selected fonts are rendered
1366 Music notation fonts can be described as a set of specific glyphs,
1367 ordered in several families. The following syntax allows various
1368 LilyPond @code{feta} non-text fonts to be used directly in markup
1371 @lilypond[quote,verbatim,relative=2]
1374 \override #'(font-encoding . fetaBraces)
1376 \override #'(font-encoding . fetaText)
1378 \override #'(font-encoding . fetaMusic)
1379 \lookup #"noteheads.s0petrucci"
1385 However, all these glyphs except the braces of various sizes contained
1386 in @code{fetaBraces} are available using the simpler syntax described
1387 in @ref{Music notation inside markup}.
1389 When using the glyphs contained in @code{fetaBraces}, the size of the
1390 brace is specified by the numerical part of the glyph name, in
1391 arbitrary units. Any integer from @code{0} to @code{575} inclusive
1392 may be specified, @code{0} giving the smallest brace. The optimum
1393 value must be determined by trial and error. These glyphs are all
1394 left braces; right braces may be obtained by rotation, see
1395 @ref{Rotating objects}.
1397 Three families of text fonts are made available: the @emph{roman}
1398 (serif) font, that defaults to New Century Schoolbook, the
1399 @emph{sans} font and the monospaced @emph{typewriter} font -- these
1400 last two families are determined by the Pango installation.
1402 @warning{There are no default fonts associated with the @emph{sans}
1403 and @emph{typewriter} font-families. An input file that specifies
1404 either of these can lead to different output on different computers.
1405 To ensure consistent output among multiple platforms, fonts must be
1406 specified by name, and those fonts must be available on any system
1407 that processes the file. See @ref{Single entry fonts} and
1408 @ref{Entire document fonts}.}
1410 Each family may include different shapes and series. The following
1411 example demonstrates the ability to select alternate families, shapes,
1412 series and sizes. The value supplied to @code{font-size} is the
1413 required change from the default size.
1415 @lilypond[quote,verbatim,relative=2]
1416 \override Score.RehearsalMark.font-family = #'typewriter
1417 \mark \markup "Ouverture"
1418 \override Voice.TextScript.font-shape = #'italic
1419 \override Voice.TextScript.font-series = #'bold
1420 d2.^\markup "Allegro"
1421 \override Voice.TextScript.font-size = #-3
1426 A similar syntax may be used in markup mode; however in this case it
1427 is preferable to use the simpler syntax explained in
1428 @ref{Selecting font and font size}:
1430 @lilypond[quote,verbatim]
1434 \override #'(font-shape . italic)
1435 \override #'(font-size . 4)
1439 \override #'(font-family . typewriter)
1441 \override #'(font-series . bold)
1445 \override #'(font-family . sans)
1452 Although it is easy to switch between preconfigured fonts, it is also
1453 possible to use other fonts, as explained in the following sections:
1454 @ref{Single entry fonts} and @ref{Entire document fonts}.
1458 @ref{The Feta font},
1459 @ref{Music notation inside markup},
1460 @ref{Rotating objects},
1461 @ref{Selecting font and font size},
1465 @node Single entry fonts
1466 @unnumberedsubsubsec Single entry fonts
1468 Any font that is installed on the operating system and recognized by
1469 FontConfig may be used in a score, using the following syntax:
1471 @lilypond[quote,verbatim,relative=2]
1472 \override Staff.TimeSignature.font-name = #"Bitstream Charter"
1473 \override Staff.TimeSignature.font-size = #2
1477 \override #'(font-name . "Vera Bold")
1482 @cindex fonts, finding available
1483 @cindex finding available fonts
1484 @cindex listing available fonts
1485 @cindex available fonts, listing
1487 @funindex show-available-fonts
1489 Running lilypond with the following option displays a list of all
1490 available fonts on the operating system:
1493 lilypond -dshow-available-fonts x
1498 @ref{Fonts explained},
1499 @ref{Entire document fonts}.
1504 @c A source file gets never installed...
1506 @c @file{lily/font-config-scheme.cc}.
1509 @node Entire document fonts
1510 @unnumberedsubsubsec Entire document fonts
1512 It is possible to change the fonts to be used as the default fonts in
1513 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1514 specifying them, in that order, as shown in the example below, which
1515 automatically scales the fonts with the value set for the global staff
1516 size. For an explanation of fonts, see @ref{Fonts explained}.
1518 @cindex font families, setting
1519 @cindex fonts, changing for entire document
1521 @funindex make-pango-font-tree
1523 @lilypond[verbatim,quote]
1526 (make-pango-font-tree "Times New Roman"
1529 (/ staff-height pt 20)))
1536 \typewriter typewriter. }
1540 @c we don't do Helvetica / Courier, since GS incorrectly loads
1545 @ref{Fonts explained},
1546 @ref{Single entry fonts},
1547 @ref{Selecting font and font size},