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 {aligning-marks-with-various-notation-objects.ly}
289 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
290 {printing-marks-on-every-staff.ly}
294 @ref{Rehearsal marks},
295 @ref{Formatting text},
296 @ref{Music notation inside markup},
303 @rinternals{MarkEvent},
304 @rinternals{Mark_engraver},
305 @rinternals{RehearsalMark}.
309 @unnumberedsubsubsec Separate text
311 @cindex separate text
312 @cindex text, separate
313 @cindex standalone text
314 @cindex top-level text
315 @cindex text, top-level
316 @cindex text, standalone
321 A @code{\markup} block can exist by itself, outside of any
322 @code{\score} block, as a @qq{top-level expression}. This syntax
323 is described in @ref{File structure}.
325 @lilypond[verbatim,quote]
327 Tomorrow, and tomorrow, and tomorrow...
332 This allows printing text separately from the music, which is
333 particularly useful when the input file contains several music pieces,
334 as described in @ref{Multiple scores in a book}.
336 @lilypond[quote,verbatim]
341 Tomorrow, and tomorrow, and tomorrow...
348 Separate text blocks can be spread over multiple pages,
349 making it possible to print text documents or books entirely
350 within LilyPond. This feature, and the specific syntax it
351 requires, are described in @ref{Multi-page markup}.
356 @funindex \markuplist
367 @lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
368 {stand-alone-two-column-markup.ly}
372 @ref{Formatting text},
373 @ref{File structure},
374 @ref{Multiple scores in a book},
375 @ref{Multi-page markup}.
381 @rinternals{TextScript}.
384 @node Formatting text
385 @subsection Formatting text
387 This section presents basic and advanced text formatting,
388 using the @code{\markup} mode specific syntax.
391 * Text markup introduction::
392 * Selecting font and font size::
394 * Graphic notation inside markup::
395 * Music notation inside markup::
396 * Multi-page markup::
399 @node Text markup introduction
400 @unnumberedsubsubsec Text markup introduction
410 A @code{\markup} block is used to typeset text with an extensible
411 syntax called @qq{markup mode}.
413 @cindex markup expressions
414 @cindex expressions, markup
415 @cindex markup syntax
416 @cindex syntax, markup
418 The markup syntax is similar to LilyPond's usual syntax: a
419 @code{\markup} expression is enclosed in curly braces
420 @code{@{@dots{} @}}. A single word is regarded as a minimal expression,
421 and therefore does not need to be enclosed with braces.
423 Unlike simple @qq{quoted text} indications, @code{\markup} blocks may
424 contain nested expressions or markup commands, entered using the
425 backslash @code{\} character. Such commands only affect the first
426 following expression.
428 @lilypond[quote,verbatim,relative=2]
430 a2^\markup { poco \italic più forte }
432 d2_\markup { \italic "string. assai" }
434 b1^\markup { \bold { molto \italic agitato } }
438 @cindex special characters in markup mode
439 @cindex markup mode, special characters
440 @cindex reserved characters, printing
441 @cindex printing reserved characters
442 @cindex printing special characters
443 @cindex quoted text in markup mode
444 @cindex markup mode, quoted text
446 A @code{\markup} block may also contain quoted text strings. Such
447 strings are treated as minimal text expressions, and therefore any
448 markup command or special character (such as @code{\} and@tie{}@code{#})
449 will be printed verbatim without affecting the formatting of the text.
450 Double quotation marks themselves may be printed by preceding them
453 @lilypond[quote,verbatim,relative=2]
454 a1^"\italic markup..."
455 a_\markup { \italic "... prints \"italic\" letters!" }
459 To be treated as a distinct expression, a list of words needs to be
460 enclosed with double quotes or preceded by a command. The way markup
461 expressions are defined affects how these expressions will be stacked,
462 centered and aligned; in the following example, the second
463 @code{\markup} expression is treated the same as the first one:
465 @lilypond[quote,verbatim,relative=2]
466 c1^\markup { \center-column { a bbb c } }
467 c1^\markup { \center-column { a { bbb c } } }
468 c1^\markup { \center-column { a \line { bbb c } } }
469 c1^\markup { \center-column { a "bbb c" } }
472 Markups can be stored in variables. Such variables may be
473 directly attached to notes:
475 @lilypond[quote,verbatim]
476 allegro = \markup { \bold \large Allegro }
486 An exhaustive list of @code{\markup}-specific commands can be found in
487 @ref{Text markup commands}.
491 @ref{Text markup commands}.
497 @file{scm/markup.scm}.
500 Syntax errors for markup mode can be confusing.
503 @node Selecting font and font size
504 @unnumberedsubsubsec Selecting font and font size
506 @cindex font switching
507 @cindex changing fonts
508 @cindex switching fonts
517 Basic font switching is supported in markup mode:
519 @lilypond[quote,verbatim,relative=2]
522 \italic { non troppo \underline Vivo }
525 d,_\markup { \italic quasi \smallCaps Tromba }
532 @funindex \abs-fontsize
542 The font size can be altered, relative to the global staff size, in a
543 number of different ways
545 It can be set to predefined size,
547 @lilypond[quote,verbatim,relative=2]
548 b1_\markup { \huge Sinfonia }
549 b1^\markup { \teeny da }
550 b1-\markup { \normalsize camera }
553 It can be set relative to its previous value,
555 @lilypond[quote,verbatim,relative=2]
556 b1_\markup { \larger Sinfonia }
557 b1^\markup { \smaller da }
558 b1-\markup { \magnify #0.6 camera }
561 It can be increased or decreased relative to the value set by the
564 @lilypond[quote,verbatim,relative=2]
565 b1_\markup { \fontsize #-2 Sinfonia }
566 b1^\markup { \fontsize #1 da }
567 b1-\markup { \fontsize #3 camera }
570 It can also be set to a fixed point-size, regardless of the global staff
573 @lilypond[quote,verbatim,relative=2]
574 b1_\markup { \abs-fontsize #20 Sinfonia }
575 b1^\markup { \abs-fontsize #8 da }
576 b1-\markup { \abs-fontsize #14 camera }
586 @funindex \normal-size-super
587 @funindex normal-size-super
589 Text may be printed as subscript or superscript. By default these are
590 printed in a smaller size, but a normal size can be used as well:
592 @lilypond[quote,verbatim]
595 \line { 1 \super st movement }
596 \line { 1 \normal-size-super st movement
597 \sub { (part two) } }
602 @cindex font families
604 The markup mode provides an easy way to select alternate font
605 families. The default serif font, of roman type, is automatically
606 selected unless specified otherwise; on the last line of the following
607 example, there is no difference between the first and the second word.
609 @lilypond[quote,verbatim]
612 \line { Act \number 1 }
613 \line { \sans { Scene I. } }
614 \line { \typewriter { Verona. An open place. } }
615 \line { Enter \roman Valentine and Proteus. }
621 Some of these font families, used for specific items such as numbers
622 or dynamics, do not provide all characters, as mentioned in
623 @ref{New dynamic marks} and @ref{Manual repeat marks}.
625 @c \concat is actually documented in Align (it is not
626 @c a font-switching command). But we need it here. -vv
628 When used inside a word, some font-switching or formatting commands
629 may produce an unwanted blank space. This can easily be solved by
630 concatenating the text elements together:
632 @lilypond[quote,verbatim]
636 \concat { 1 \super st }
640 \concat { \dynamic p , }
641 \italic { con dolce espressione }
647 An exhaustive list of font switching commands and custom font usage
648 commands can be found in @ref{Font}.
650 Defining custom font sets is also possible, as explained in
659 @funindex \normalsize
685 @ref{New dynamic marks},
686 @ref{Manual repeat marks},
690 @file{scm/define-markup-commands.scm}.
696 @rinternals{TextScript}.
699 Using the font sizing commands @code{\teeny}, @code{\tiny},
700 @code{\small}, @code{\normalsize}, @code{\large}, and
701 @code{\huge} will lead to inconsistent line spacing compared to
702 using @code{\fontsize}.
706 @unnumberedsubsubsec Text alignment
708 @cindex text, aligning
709 @cindex aligning text
710 @cindex aligning markup text
711 @cindex aligning markups
712 @cindex markups, aligning
713 @cindex markup text, aligning
715 This subsection discusses how to place text in markup mode. Markup
716 objects can also be moved as a whole, using the syntax described in
717 @rlearning{Moving objects}.
719 @c Padding commands should be mentioned on this page, but
720 @c most of these require \box to be more clearly illustrated. -vv
722 @cindex text, horizontal alignment
723 @cindex horizontal text alignment
725 @funindex \left-align
727 @funindex \center-align
728 @funindex center-align
729 @funindex \right-align
730 @funindex right-align
732 Markup objects may be aligned in different ways. By default, a text
733 indication is aligned on its left edge: in the following example,
734 there is no difference between the first and the second markup.
736 @lilypond[quote,verbatim,relative=2]
739 d-\markup { \left-align poco }
741 d-\markup { \center-align { poco } }
743 d-\markup { \right-align poco }
749 Horizontal alignment may be fine-tuned using a numeric value:
751 @lilypond[quote,verbatim,relative=2]
752 a1-\markup { \halign #-1 poco }
754 a,-\markup { \halign #0 poco }
756 a,-\markup { \halign #0.5 poco }
758 a,-\markup { \halign #2 poco }
762 Some objects may have alignment procedures of their own, and therefore
763 are not affected by these commands. It is possible to move such
764 markup objects as a whole, as shown for instance in
767 @cindex text, vertical alignment
768 @cindex vertical text alignment
777 @c QUERY Should the function of ``\null'' be clarified? rp
779 Vertical alignment is a bit more complex. As stated above, markup
780 objects can be moved as a whole; however, it is also possible to move
781 specific elements inside a markup block. In this case, the element to
782 be moved needs to be preceded with an @emph{anchor point}, that can be
783 another markup element or an invisible object. The following example
784 demonstrates these two possibilities; the last markup in this example
785 has no anchor point, and therefore is not moved.
787 @lilypond[quote,verbatim,relative=1]
790 \raise #2 { Scène 1 }
795 \lower #4 \bold { Très modéré }
799 \raise #4 \italic { Une forêt. }
804 @funindex \general-align
805 @funindex general-align
808 @funindex \translate-scaled
809 @funindex translate-scaled
811 Some commands can affect both the horizontal and vertical alignment of
812 text objects in markup mode. Any object affected by these commands
813 must be preceded with an anchor point:
815 @lilypond[quote,verbatim,relative=1]
818 \translate #'(-1 . 2) "Scène 1"
823 \general-align #Y #3.2 \bold "Très modéré"
828 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
833 @cindex multi-line markup
834 @cindex markup, multi-line
835 @cindex multi-line text
836 @cindex text, multi-line
837 @cindex text in columns
838 @cindex columns, text
842 @funindex \center-column
843 @funindex center-column
845 A markup object may include several lines of text. In the following
846 example, each element or expression is placed on its own line, either
847 left-aligned or centered:
849 @lilypond[quote,verbatim]
865 @cindex centering text on the page
866 @cindex text, centering on the page
867 @cindex markup, centering on the page
872 Similarly, a list of elements or expressions may be spread to fill the
873 entire horizontal line width (if there is only one element, it will be
874 centered on the page). These expressions can, in turn, include
875 multi-line text or any other markup expression:
877 @lilypond[quote,verbatim]
880 \line { William S. Gilbert }
882 \huge \smallCaps "The Mikado"
884 \smallCaps "The Town of Titipu"
886 \line { Sir Arthur Sullivan }
894 @cindex wordwrapped text
895 @cindex justified text
896 @cindex text, justified
897 @cindex text, wordwrapped
898 @cindex markup text, wordwrapped
899 @cindex markup text, justified
906 Long text indications can also be automatically wrapped accordingly to
907 the given line width. These will be either left-aligned or justified,
908 as shown in the following example.
910 @lilypond[quote,verbatim]
913 \line \smallCaps { La vida breve }
914 \line \bold { Acto I }
916 (La escena representa el corral de una casa de
917 gitanos en el AlbaicÃn de Granada. Al fondo una
918 puerta por la que se ve el negro interior de
919 una Fragua, iluminado por los rojos resplandores
924 \line \bold { Acto II }
925 \override #'(line-width . 50)
927 (Calle de Granada. Fachada de la casa de Carmela
928 y su hermano Manuel con grandes ventanas abiertas
929 a través de las que se ve el patio
930 donde se celebra una alegre fiesta)
936 @cindex text alignment commands
937 @cindex markup text alignment commands
938 @cindex alignment, text, commands
940 An exhaustive list of text alignment commands can be found in
945 @rlearning{Moving objects}.
952 @file{scm/define-markup-commands.scm}.
958 @rinternals{TextScript}.
961 @node Graphic notation inside markup
962 @unnumberedsubsubsec Graphic notation inside markup
964 @cindex graphics, embedding
965 @cindex drawing graphic objects
966 @cindex graphic objects, drawing
967 @cindex embedding graphic objects
968 @cindex graphic objects, embedding
970 Various graphic objects may be added to a score, using markup
973 @cindex decorating text
975 @cindex text, framing
976 @cindex text, decorating
977 @cindex markup text, decorating
978 @cindex markup text, framing
984 @funindex \rounded-box
985 @funindex rounded-box
991 Some markup commands allow decoration of text elements with graphics,
992 as demonstrated in the following example.
994 @lilypond[quote,verbatim]
1003 \bracket "1866 - 1925"
1006 \rounded-box \bold Prelude
1011 @cindex padding around text
1012 @cindex text padding
1013 @cindex markup text padding
1015 @funindex \pad-markup
1016 @funindex pad-markup
1019 @funindex \pad-to-box
1020 @funindex pad-to-box
1021 @funindex \pad-around
1022 @funindex pad-around
1024 Some commands may require an increase in the padding around the text;
1025 this is achieved with some markup commands exhaustively described in
1028 @lilypond[quote,verbatim]
1029 \markup \fill-line {
1031 \box "Charles Ives (1874 - 1954)"
1033 \box \pad-markup #2 "THE UNANSWERED QUESTION"
1034 \box \pad-x #8 "A Cosmic Landscape"
1041 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
1042 \bold "Largo to Presto"
1045 "String quartet keeps very even time,
1046 Flute quartet keeps very uneven time."
1050 @cindex graphic notation
1051 @cindex symbols, non-musical
1052 @cindex non-musical symbols
1053 @cindex notation, graphic
1057 @funindex \draw-circle
1058 @funindex draw-circle
1059 @funindex \filled-box
1060 @funindex filled-box
1063 @funindex \draw-line
1065 @funindex \arrow-head
1066 @funindex arrow-head
1068 Other graphic elements or symbols may be printed without requiring any
1069 text. As with any markup expression, such objects can be combined.
1071 @lilypond[quote,verbatim]
1074 \draw-circle #4 #0.4 ##f
1075 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
1081 \draw-line #'(0 . 4)
1082 \arrow-head #Y #DOWN ##f
1087 @cindex embedded graphics
1088 @cindex images, embedding
1089 @cindex graphics, embedding
1094 @funindex \postscript
1095 @funindex postscript
1097 Advanced graphic features include the ability to include external
1098 image files converted to the Encapsulated PostScript format
1099 (@emph{eps}), or to directly embed graphics into the input file, using
1100 native PostScript code. In such a case, it may be useful to
1101 explicitly specify the size of the drawing, as demonstrated below:
1103 @lilypond[quote,verbatim,relative=1]
1106 \epsfile #X #10 #"./context-example.eps"
1107 \with-dimensions #'(0 . 6) #'(0 . 10)
1123 An exhaustive list of graphics-specific commands can be found in
1129 @ref{Editorial annotations},
1133 @file{scm/define-markup-commands.scm},
1134 @file{scm/stencil.scm}.
1139 Internals Reference:
1140 @rinternals{TextScript}.
1143 @node Music notation inside markup
1144 @unnumberedsubsubsec Music notation inside markup
1146 @cindex notation inside markup
1147 @cindex music inside markup
1148 @cindex markup, music notation inside
1150 Various musical notation elements may be added to a score, inside a
1153 Notes and accidentals can be entered using markup commands:
1155 @lilypond[quote,verbatim,relative=2]
1159 \note-by-number #1 #1 #1.5
1162 \natural \semiflat \flat
1163 \sesquiflat \doubleflat
1167 \natural \semisharp \sharp
1168 \sesquisharp \doublesharp
1173 Other notation objects may also be printed
1176 @lilypond[quote,verbatim,relative=1]
1178 ees\finger \markup \tied-lyric #"4~1"
1179 fis_\markup { \dynamic rf }
1190 More generally, any available musical symbol may be included
1191 separately in a markup object, as demonstrated below; an exhaustive
1192 list of these symbols and their names can be found in
1193 @ref{The Feta font}.
1195 @lilypond[quote,verbatim,relative=2]
1197 c'^\markup { \musicglyph #"eight" }
1199 c,8._\markup { \musicglyph #"clefs.G_change" }
1201 c2^\markup { \musicglyph #"timesig.neomensural94" }
1204 Another way of printing non-text glyphs is described in
1205 @ref{Fonts explained}. This is useful for printing braces of various
1208 The markup mode also supports diagrams for specific
1211 @lilypond[quote,verbatim,relative=2]
1213 \fret-diagram-terse #"x;x;o;2;3;2;"
1216 \harp-pedal #"^-v|--ov^"
1221 \musicglyph #"accordion.discant"
1223 \raise #0.5 \musicglyph #"accordion.dot"
1224 \raise #1.5 \musicglyph #"accordion.dot"
1228 @c The accordion diagram is actually taken from a snippet.
1231 Such diagrams are documented in @ref{Instrument Specific Markup}.
1233 @cindex score inside markup
1234 @cindex markup, score inside
1236 A whole score can even be nested inside a markup object. In such a
1237 case, the nested @code{\score} block must contain a @code{\layout}
1238 block, as demonstrated here:
1240 @lilypond[quote,verbatim,relative=1]
1243 \relative c' { c4 d e f }
1251 An exhaustive list of music notation related commands can be found in
1257 @ref{The Feta font},
1258 @ref{Fonts explained}.
1261 @file{scm/define-markup-commands.scm},
1262 @file{scm/fret-diagrams.scm},
1263 @file{scm/harp-pedals.scm}.
1268 Internals Reference:
1269 @rinternals{TextScript}.
1272 @node Multi-page markup
1273 @unnumberedsubsubsec Multi-page markup
1275 @cindex multi-page markup
1276 @cindex markup, multi-page
1277 @cindex markup text, multi-page
1278 @cindex text spread over multiple pages
1280 @funindex \markuplist
1281 @funindex markuplist
1282 @funindex \justified-lines
1283 @funindex justified-lines
1284 @funindex \wordwrap-lines
1285 @funindex wordwrap-lines
1287 Although standard markup objects are not breakable, a specific syntax
1288 makes it possible to enter lines of text that can spread over multiple
1291 @lilypond[quote,verbatim]
1294 A very long text of justified lines.
1298 Another very long paragraph.
1305 This syntax accepts a list of markups, that can be
1308 the result of a markup list command,
1312 a list of markup lists.
1315 An exhaustive list of markup list commands can be found in
1316 @ref{Text markup list commands}.
1320 @ref{Text markup list commands}.
1323 @rextend{New markup list command definition}.
1326 @file{scm/define-markup-commands.scm}.
1331 Internals Reference:
1332 @rinternals{TextScript}.
1334 @funindex \markuplist
1335 @funindex markuplist
1345 This section presents the way fonts are handled, and how they may be
1350 * Single entry fonts::
1351 * Entire document fonts::
1354 @node Fonts explained
1355 @unnumberedsubsubsec Fonts explained
1358 @cindex fonts, explained
1359 @cindex braces, various sizes
1360 @cindex fonts, non-text in markup
1361 @cindex non-text fonts in markup
1363 @funindex font-interface
1365 Fonts are handled through several libraries. FontConfig is used to
1366 detect available fonts on the system; the selected fonts are rendered
1369 Music notation fonts can be described as a set of specific glyphs,
1370 ordered in several families. The following syntax allows various
1371 LilyPond @code{feta} non-text fonts to be used directly in markup
1374 @lilypond[quote,verbatim,relative=2]
1377 \override #'(font-encoding . fetaBraces)
1379 \override #'(font-encoding . fetaText)
1381 \override #'(font-encoding . fetaMusic)
1382 \lookup #"noteheads.s0petrucci"
1388 However, all these glyphs except the braces of various sizes contained
1389 in @code{fetaBraces} are available using the simpler syntax described
1390 in @ref{Music notation inside markup}.
1392 When using the glyphs contained in @code{fetaBraces}, the size of the
1393 brace is specified by the numerical part of the glyph name, in
1394 arbitrary units. Any integer from @code{0} to @code{575} inclusive
1395 may be specified, @code{0} giving the smallest brace. The optimum
1396 value must be determined by trial and error. These glyphs are all
1397 left braces; right braces may be obtained by rotation, see
1398 @ref{Rotating objects}.
1400 Three families of text fonts are made available: the @emph{roman}
1401 (serif) font, that defaults to New Century Schoolbook, the
1402 @emph{sans} font and the monospaced @emph{typewriter} font -- these
1403 last two families are determined by the Pango installation.
1405 @warning{There are no default fonts associated with the @emph{sans}
1406 and @emph{typewriter} font-families. An input file that specifies
1407 either of these can lead to different output on different computers.
1408 To ensure consistent output among multiple platforms, fonts must be
1409 specified by name, and those fonts must be available on any system
1410 that processes the file. See @ref{Single entry fonts} and
1411 @ref{Entire document fonts}.}
1413 Each family may include different shapes and series. The following
1414 example demonstrates the ability to select alternate families, shapes,
1415 series and sizes. The value supplied to @code{font-size} is the
1416 required change from the default size.
1418 @lilypond[quote,verbatim,relative=2]
1419 \override Score.RehearsalMark.font-family = #'typewriter
1420 \mark \markup "Ouverture"
1421 \override Voice.TextScript.font-shape = #'italic
1422 \override Voice.TextScript.font-series = #'bold
1423 d2.^\markup "Allegro"
1424 \override Voice.TextScript.font-size = #-3
1429 A similar syntax may be used in markup mode; however in this case it
1430 is preferable to use the simpler syntax explained in
1431 @ref{Selecting font and font size}:
1433 @lilypond[quote,verbatim]
1437 \override #'(font-shape . italic)
1438 \override #'(font-size . 4)
1442 \override #'(font-family . typewriter)
1444 \override #'(font-series . bold)
1448 \override #'(font-family . sans)
1455 Although it is easy to switch between preconfigured fonts, it is also
1456 possible to use other fonts, as explained in the following sections:
1457 @ref{Single entry fonts} and @ref{Entire document fonts}.
1461 @ref{The Feta font},
1462 @ref{Music notation inside markup},
1463 @ref{Rotating objects},
1464 @ref{Selecting font and font size},
1468 @node Single entry fonts
1469 @unnumberedsubsubsec Single entry fonts
1471 Any font that is installed on the operating system and recognized by
1472 FontConfig may be used in a score, using the following syntax:
1474 @lilypond[quote,verbatim,relative=2]
1475 \override Staff.TimeSignature.font-name = #"Bitstream Charter"
1476 \override Staff.TimeSignature.font-size = #2
1480 \override #'(font-name . "Vera Bold")
1485 @cindex fonts, finding available
1486 @cindex finding available fonts
1487 @cindex listing available fonts
1488 @cindex available fonts, listing
1490 @funindex show-available-fonts
1492 The following command displays a list of all available fonts on the
1496 lilypond -dshow-available-fonts x
1501 @ref{Fonts explained},
1502 @ref{Entire document fonts}.
1507 @c A source file gets never installed...
1509 @c @file{lily/font-config-scheme.cc}.
1512 @node Entire document fonts
1513 @unnumberedsubsubsec Entire document fonts
1515 It is possible to change the fonts to be used as the default fonts in
1516 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1517 specifying them, in that order, as shown in the example below, which
1518 automatically scales the fonts with the value set for the global staff
1519 size. For an explanation of fonts, see @ref{Fonts explained}.
1521 @cindex font families, setting
1522 @cindex fonts, changing for entire document
1524 @funindex make-pango-font-tree
1526 @lilypond[verbatim,quote]
1529 (make-pango-font-tree "Times New Roman"
1532 (/ staff-height pt 20)))
1539 \typewriter typewriter. }
1543 @c we don't do Helvetica / Courier, since GS incorrectly loads
1548 @ref{Fonts explained},
1549 @ref{Single entry fonts},
1550 @ref{Selecting font and font size},