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
67 formatting may be added to a note by explicitly using a
68 @code{\markup} block, as described 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.
76 However, their widths can be taken into account:
77 in the following example, the first text string does not affect
78 spacing, whereas the second one does.
80 @lilypond[quote,verbatim,relative=2]
86 In addition to text scripts, articulations can be attached to notes.
87 For more information, see @ref{Articulations and ornamentations}.
89 For more information about the relative ordering of text scripts and
90 articulations, see @rlearning{Placement of objects}.
92 @funindex \textLengthOn
93 @funindex textLengthOn
94 @funindex \textLengthOff
95 @funindex textLengthOff
99 @code{\textLengthOff}.
105 @rlearning{Placement of objects}.
108 @ref{Formatting text},
109 @ref{Direction and placement}.
115 @rinternals{TextScript}.
118 @cindex text outside margin
119 @cindex margin, text running over
120 @cindex text, keeping inside margin
121 @cindex lyrics, keeping inside margin
126 Checking to make sure that text scripts and lyrics are within the
127 margins is a relatively large computational task. To speed up
128 processing, LilyPond does not perform such calculations by
129 default; to enable it, use
132 \override Score.PaperColumn #'keep-inside-line = ##t
137 @unnumberedsubsubsec Text spanners
139 @cindex text spanners
141 Some performance indications, e.g., @notation{rallentando} or
142 @notation{accelerando}, are written as text and are extended over
143 multiple notes with dotted lines. Such objects, called @qq{spanners},
144 may be created from one note to another using the following syntax:
146 @lilypond[verbatim,quote,relative=2]
147 \override TextSpanner #'(bound-details left text) = "rit."
152 @cindex text spanners, formatting
153 @cindex formatting text spanners
156 The string to be printed is set through object properties. By default
157 it is printed in italic characters, but different formatting can be
158 obtained using @code{\markup} blocks, as described in @ref{Formatting
161 @lilypond[quote,relative=2,verbatim]
162 \override TextSpanner #'(bound-details left text) =
163 \markup { \upright "rit." }
168 The line style, as well as the text string, can be defined as an
169 object property. This syntax is described in @ref{Line styles}.
172 @funindex \textSpannerUp
173 @funindex textSpannerUp
174 @funindex \textSpannerDown
175 @funindex textSpannerDown
176 @funindex \textSpannerNeutral
177 @funindex textSpannerNeutral
181 @code{\textSpannerUp},
182 @code{\textSpannerDown},
183 @code{\textSpannerNeutral}.
187 LilyPond is only able to handle one text spanner per voice.
198 @rinternals{TextSpanner}.
202 @unnumberedsubsubsec Text marks
207 @cindex text on bar line
208 @cindex coda on bar line
209 @cindex segno on bar line
210 @cindex fermata on bar line
211 @cindex bar lines, symbols on
218 Various text elements may be added to a score using
219 the syntax described in @ref{Rehearsal marks}:
221 @c \mark needs to be placed on a separate line (it's not
222 @c attached to an object like \markup is). -vv
224 @lilypond[verbatim,quote,relative=2]
230 This syntax makes it possible to put any text on a bar line;
231 more complex text formatting may be added using a @code{\markup}
232 block, as described in @ref{Formatting text}:
234 @lilypond[quote,verbatim,relative=1]
236 \mark \markup { \italic { colla parte } }
242 This syntax also allows to print special signs, like coda, segno
243 or fermata, by specifying the appropriate symbol name as explained in
244 @ref{Music notation inside markup}:
246 @lilypond[quote,verbatim,relative=2]
248 \mark \markup { \musicglyph #"scripts.ufermata" }
253 Such objects are only typeset above the top staff of the score; depending on
254 whether they are specified at the end or the middle of a bar, they
255 can be placed above the bar line or between notes. When specified at a
256 line break, the mark will be printed at the beginning of the next line.
258 @lilypond[quote,verbatim,relative=2]
268 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
269 {printing-marks-at-the-end-of-a-line.ly}
271 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
272 {aligning-marks-with-various-notation-objects.ly}
274 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
275 {printing-marks-on-every-staff.ly}
280 @ref{Rehearsal marks},
281 @ref{Formatting text},
282 @ref{Music notation inside markup},
289 @rinternals{MarkEvent},
290 @rinternals{Mark_engraver},
291 @rinternals{RehearsalMark}.
295 @unnumberedsubsubsec Separate text
297 @cindex separate text
298 @cindex text, separate
299 @cindex standalone text
300 @cindex top-level text
301 @cindex text, top-level
302 @cindex text, standalone
307 A @code{\markup} block can exist by itself, outside of any
308 @code{\score} block, as a @qq{top-level expression}. This syntax
309 is described in @ref{File structure}.
311 @lilypond[verbatim,quote]
313 Tomorrow, and tomorrow, and tomorrow...
318 This allows printing text separately from the music, which is
319 particularly useful when the input file contains several music pieces,
320 as described in @ref{Multiple scores in a book}.
322 @lilypond[quote,verbatim]
327 Tomorrow, and tomorrow, and tomorrow...
334 Separate text blocks can be spread over multiple pages,
335 making it possible to print text documents or books entirely
336 within LilyPond. This feature, and the specific syntax it
337 requires, are described in @ref{Multi-page markup}.
342 @funindex \markuplines
343 @funindex markuplines
353 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
354 {stand-alone-two-column-markup.ly}
359 @ref{Formatting text},
360 @ref{File structure},
361 @ref{Multiple scores in a book},
362 @ref{Multi-page markup}.
368 @rinternals{TextScript}.
371 @node Formatting text
372 @subsection Formatting text
374 This section presents basic and advanced text formatting,
375 using the @code{\markup} mode specific syntax.
378 * Text markup introduction::
379 * Selecting font and font size::
381 * Graphic notation inside markup::
382 * Music notation inside markup::
383 * Multi-page markup::
386 @node Text markup introduction
387 @unnumberedsubsubsec Text markup introduction
397 A @code{\markup} block is used to typeset text with an extensible
398 syntax called @qq{markup mode}.
400 @cindex markup expressions
401 @cindex expressions, markup
402 @cindex markup syntax
403 @cindex syntax, markup
405 The markup syntax is similar to LilyPond's usual syntax: a
406 @code{\markup} expression is enclosed in curly braces @code{@{
407 @dots{} @}}. A single word is regarded as a minimal expression,
408 and therefore does not need to be enclosed with braces.
410 Unlike simple @qq{quoted text} indications, @code{\markup} blocks may
411 contain nested expressions or markup commands, entered using the
412 backslash @code{\} character. Such commands only affect the first
413 following expression.
415 @lilypond[quote,verbatim,relative=2]
417 a2^\markup { poco \italic più forte }
419 d2_\markup { \italic "string. assai" }
421 b1^\markup { \bold { molto \italic agitato } }
425 @cindex special characters in markup mode
426 @cindex markup mode, special characters
427 @cindex reserved characters, printing
428 @cindex printing reserved characters
429 @cindex printing special characters
430 @cindex quoted text in markup mode
431 @cindex markup mode, quoted text
433 A @code{\markup} block may also contain quoted text strings. Such
434 strings are treated as minimal text expressions, and therefore any
435 markup command or special character (such as @code{\} and @code{#})
436 will be printed verbatim without affecting the formatting of the text.
437 Double quotation marks themselves may be printed by preceding them
440 @lilypond[quote,verbatim,relative=2]
441 a1^"\italic markup..."
442 a_\markup { \italic "... prints \"italic\" letters!" }
446 To be treated as a distinct expression, a list of words needs to be
447 enclosed with double quotes or preceded by a command. The way markup
448 expressions are defined affects how these expressions will be stacked,
449 centered and aligned; in the following example, the second
450 @code{\markup} expression is treated the same as the first one:
452 @lilypond[quote,verbatim,relative=2]
453 c1^\markup { \center-column { a bbb c } }
454 c1^\markup { \center-column { a { bbb c } } }
455 c1^\markup { \center-column { a \line { bbb c } } }
456 c1^\markup { \center-column { a "bbb c" } }
459 Markups can be stored in variables. Such variables may be
460 directly attached to notes:
462 @lilypond[quote,verbatim]
463 allegro = \markup { \bold \large Allegro }
473 An exhaustive list of @code{\markup}-specific commands can be found in
474 @ref{Text markup commands}.
479 @ref{Text markup commands}.
485 @file{scm/@/markup@/.scm}.
490 Syntax errors for markup mode can be confusing.
493 @node Selecting font and font size
494 @unnumberedsubsubsec Selecting font and font size
496 @cindex font switching
497 @cindex changing fonts
498 @cindex switching fonts
507 Basic font switching is supported in markup mode:
509 @lilypond[quote,verbatim,relative=2]
512 \italic { non troppo \underline Vivo }
515 d,_\markup { \italic quasi \smallCaps Tromba }
531 The size of the characters can also be altered in different ways:
534 the font size can be set to predefined standard sizes,
537 the font size can be set to an absolute value,
540 the font size can also be changed relatively to its previous value.
544 The following example demonstrates these three methods:
546 @lilypond[quote,verbatim,relative=1]
553 \fontsize #5 Sinfonia
560 \magnify #0.6 { e sentimento } )
573 Text may be printed as subscript or superscript. By default these are
574 printed in a smaller size, but a normal size can be used as well:
576 @lilypond[quote,verbatim]
579 \line { 1 \super st movement }
580 \line { 1 \normal-size-super st movement
581 \sub { (part two) } }
586 @cindex font families
588 The markup mode provides an easy way to select alternate font
589 families. The default serif font, of roman type, is automatically
590 selected unless specified otherwise; on the last line of the following
591 example, there is no difference between the first and the second word.
593 @lilypond[quote,verbatim]
596 \line { Act \number 1 }
597 \line { \sans { Scene I. } }
598 \line { \typewriter { Verona. An open place. } }
599 \line { Enter \roman Valentine and Proteus. }
605 Some of these font families, used for specific items such as numbers
606 or dynamics, do not provide all characters, as mentioned in @ref{New
607 dynamic marks} and @ref{Manual repeat marks}.
609 @c \concat is actually documented in Align (it is not
610 @c a font-switching command). But we need it here. -vv
612 When used inside a word, some font-switching or formatting commands
613 may produce an unwanted blank space. This can easily be solved by
614 concatenating the text elements together:
616 @lilypond[quote,verbatim]
620 \concat { 1 \super st }
624 \concat { \dynamic p , }
625 \italic { con dolce espressione }
631 An exhaustive list of font switching commands and custom font usage
632 commands can be found in @ref{Font}.
634 Defining custom font sets is also possible, as explained in
643 @funindex \normalsize
670 @ref{New dynamic marks},
671 @ref{Manual repeat marks},
678 @rinternals{TextScript}.
681 @file{scm/@/define@/-markup@/-commands@/.scm}.
685 @unnumberedsubsubsec Text alignment
687 @cindex text, aligning
688 @cindex aligning text
689 @cindex aligning markup text
690 @cindex aligning markups
691 @cindex markups, aligning
692 @cindex markup text, aligning
694 This subsection discusses how to place text in markup mode. Markup
695 objects can also be moved as a whole, using the syntax described in
696 @rlearning{Moving objects}.
698 @c Padding commands should be mentioned on this page, but
699 @c most of these require \box to be more clearly illustrated. -vv
701 @cindex text, horizontal alignment
702 @cindex horizontal text alignment
704 @funindex \left-align
706 @funindex \center-align
707 @funindex center-align
708 @funindex \right-align
709 @funindex right-align
711 Markup objects may be aligned in different ways. By default, a text
712 indication is aligned on its left edge: in the following example,
713 there is no difference between the first and the second markup.
715 @lilypond[quote,verbatim,relative=2]
718 d-\markup { \left-align poco }
720 d-\markup { \center-align { poco } }
722 d-\markup { \right-align poco }
728 Horizontal alignment may be fine-tuned using a numeric value:
730 @lilypond[quote,verbatim,relative=2]
731 a1-\markup { \halign #-1 poco }
733 a,-\markup { \halign #0 poco }
735 a,-\markup { \halign #0.5 poco }
737 a,-\markup { \halign #2 poco }
741 Some objects may have alignment procedures of their own, and therefore
742 are not affected by these commands. It is possible to move such
743 markup objects as a whole, as shown for instance in @ref{Text marks}.
745 @cindex text, vertical alignment
746 @cindex vertical text alignment
755 @c QUERY Should the function of ``\null'' be clarified? rp
757 Vertical alignment is a bit more complex. As stated above, markup
758 objects can be moved as a whole; however, it is also possible to move
759 specific elements inside a markup block. In this case, the element to
760 be moved needs to be preceded with an @emph{anchor point}, that can be
761 another markup element or an invisible object. The following example
762 demonstrates these two possibilities; the last markup in this example
763 has no anchor point, and therefore is not moved.
765 @lilypond[quote,verbatim,relative=1]
768 \raise #2 { Scène 1 }
773 \lower #4 \bold { Très modéré }
777 \raise #4 \italic { Une forêt. }
782 @funindex \general-align
783 @funindex general-align
786 @funindex \translate-scaled
787 @funindex translate-scaled
789 Some commands can affect both the horizontal and vertical alignment of
790 text objects in markup mode. Any object affected by these commands
791 must be preceded with an anchor point:
793 @lilypond[quote,verbatim,relative=1]
796 \translate #'(-1 . 2) "Scène 1"
801 \general-align #Y #3.2 \bold "Très modéré"
806 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
811 @cindex multi-line markup
812 @cindex markup, multi-line
813 @cindex multi-line text
814 @cindex text, multi-line
815 @cindex text in columns
816 @cindex columns, text
820 @funindex \center-column
821 @funindex center-column
823 A markup object may include several lines of text. In the following
824 example, each element or expression is placed on its own line, either
825 left-aligned or centered:
827 @lilypond[quote,verbatim]
843 @cindex centering text on the page
844 @cindex text, centering on the page
845 @cindex markup, centering on the page
850 Similarly, a list of elements or expressions may be spread to fill the
851 entire horizontal line width (if there is only one element, it will be
852 centered on the page). These expressions can, in turn, include
853 multi-line text or any other markup expression:
855 @lilypond[quote,verbatim]
858 \line { William S. Gilbert }
860 \huge \smallCaps "The Mikado"
862 \smallCaps "The Town of Titipu"
864 \line { Sir Arthur Sullivan }
872 @cindex wordwrapped text
873 @cindex justified text
874 @cindex text, justified
875 @cindex text, wordwrapped
876 @cindex markup text, wordwrapped
877 @cindex markup text, justified
884 Long text indications can also be automatically wrapped accordingly to
885 the given line width. These will be either left-aligned or justified,
886 as shown in the following example.
888 @lilypond[quote,verbatim]
891 \line \smallCaps { La vida breve }
892 \line \bold { Acto I }
894 (La escena representa el corral de una casa de
895 gitanos en el AlbaicÃn de Granada. Al fondo una
896 puerta por la que se ve el negro interior de
897 una Fragua, iluminado por los rojos resplandores
902 \line \bold { Acto II }
903 \override #'(line-width . 50)
905 (Calle de Granada. Fachada de la casa de Carmela
906 y su hermano Manuel con grandes ventanas abiertas
907 a través de las que se ve el patio
908 donde se celebra una alegre fiesta)
914 @cindex text alignment commands
915 @cindex markup text alignment commands
916 @cindex alignment, text, commands
918 An exhaustive list of text alignment commands can be found in
924 @rlearning{Moving objects}.
934 @rinternals{TextScript}.
937 @file{scm/@/define@/-markup@/-commands@/.scm}.
940 @node Graphic notation inside markup
941 @unnumberedsubsubsec Graphic notation inside markup
943 @cindex graphics, embedding
944 @cindex drawing graphic objects
945 @cindex graphic objects, drawing
946 @cindex embedding graphic objects
947 @cindex graphic objects, embedding
949 Various graphic objects may be added to a score, using markup
952 @cindex decorating text
954 @cindex text, framing
955 @cindex text, decorating
956 @cindex markup text, decorating
957 @cindex markup text, framing
963 @funindex \rounded-box
964 @funindex rounded-box
970 Some markup commands allow decoration of text elements with graphics,
971 as demonstrated in the following example.
973 @lilypond[quote,verbatim]
982 \bracket "1866 - 1925"
985 \rounded-box \bold Prelude
990 @cindex padding around text
992 @cindex markup text padding
994 @funindex \pad-markup
998 @funindex \pad-to-box
1000 @funindex \pad-around
1001 @funindex pad-around
1003 Some commands may require an increase in the padding around the text;
1004 this is achieved with some markup commands exhaustively described in
1007 @lilypond[quote,verbatim]
1008 \markup \fill-line {
1010 \box "Charles Ives (1874 - 1954)"
1012 \box \pad-markup #2 "THE UNANSWERED QUESTION"
1013 \box \pad-x #8 "A Cosmic Landscape"
1020 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
1021 \bold "Largo to Presto"
1024 "String quartet keeps very even time,
1025 Flute quartet keeps very uneven time."
1029 @cindex graphic notation
1030 @cindex symbols, non-musical
1031 @cindex non-musical symbols
1032 @cindex notation, graphic
1036 @funindex \draw-circle
1037 @funindex draw-circle
1038 @funindex \filled-box
1039 @funindex filled-box
1042 @funindex \draw-line
1044 @funindex \arrow-head
1045 @funindex arrow-head
1047 Other graphic elements or symbols may be printed without requiring any
1048 text. As with any markup expression, such objects can be combined.
1050 @lilypond[quote,verbatim]
1053 \draw-circle #4 #0.4 ##f
1054 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
1060 \draw-line #'(0 . 4)
1061 \arrow-head #Y #DOWN ##f
1066 @cindex embedded graphics
1067 @cindex images, embedding
1068 @cindex graphics, embedding
1073 @funindex \postscript
1074 @funindex postscript
1076 Advanced graphic features include the ability to include external
1077 image files converted to the Encapsulated PostScript format
1078 (@emph{eps}), or to directly embed graphics into the input file, using
1079 native PostScript code. In such a case, it may be useful to
1080 explicitly specify the size of the drawing, as demonstrated below:
1082 @lilypond[quote,verbatim,relative=1]
1085 \epsfile #X #10 #"./context-example.eps"
1086 \with-dimensions #'(0 . 6) #'(0 . 10)
1102 An exhaustive list of graphics-specific commands can be found in
1109 @ref{Editorial annotations}.
1114 Internals Reference:
1115 @rinternals{TextScript}.
1118 @file{scm/@/define@/-markup@/-commands@/.scm},
1119 @file{scm/@/stencil@/.scm}.
1122 @node Music notation inside markup
1123 @unnumberedsubsubsec Music notation inside markup
1125 @cindex notation inside markup
1126 @cindex music inside markup
1127 @cindex markup, music notation inside
1129 Various musical notation elements may be added to a score, inside a
1132 Notes and accidentals can be entered using markup commands:
1134 @lilypond[quote,verbatim,relative=2]
1138 \note-by-number #1 #1 #1.5
1141 \natural \semiflat \flat
1142 \sesquiflat \doubleflat
1146 \natural \semisharp \sharp
1147 \sesquisharp \doublesharp
1152 Other notation objects may also be printed
1155 @lilypond[quote,verbatim,relative=1]
1162 fis_\markup { \dynamic rf }
1173 More generally, any available musical symbol may be included
1174 separately in a markup object, as demonstrated below; an exhaustive
1175 list of these symbols and their names can be found in @ref{The Feta
1178 @lilypond[quote,verbatim,relative=2]
1180 c'^\markup { \musicglyph #"eight" }
1182 c,8._\markup { \musicglyph #"clefs.G_change" }
1184 c2^\markup { \musicglyph #"timesig.neomensural94" }
1187 Another way of printing non-text glyphs is described in @ref{Fonts
1188 explained}. This is useful for printing braces of various sizes.
1190 The markup mode also supports diagrams for specific
1193 @lilypond[quote,verbatim,relative=2]
1195 \fret-diagram-terse #"x;x;o;2;3;2;"
1198 \harp-pedal #"^-v|--ov^"
1203 \musicglyph #"accordion.accDiscant"
1205 \raise #0.5 \musicglyph #"accordion.accDot"
1206 \raise #1.5 \musicglyph #"accordion.accDot"
1210 @c The accordion diagram is actually taken from a snippet.
1213 Such diagrams are documented in @ref{Instrument Specific Markup}.
1215 @cindex score inside markup
1216 @cindex markup, score inside
1218 A whole score can even be nested inside a markup object. In such a
1219 case, the nested @code{\score} block must contain a @code{\layout}
1220 block, as demonstrated here:
1222 @lilypond[quote,verbatim,relative=1]
1225 \relative c' { c4 d e f }
1233 An exhaustive list of music notation related commands can be found in
1240 @ref{The Feta font},
1241 @ref{Fonts explained}.
1246 Internals Reference:
1247 @rinternals{TextScript}.
1250 @file{scm/@/define@/-markup@/-commands@/.scm},
1251 @file{scm/@/fret@/-diagrams@/.scm},
1252 @file{scm/@/harp@/-pedals@/.scm}.
1255 @node Multi-page markup
1256 @unnumberedsubsubsec Multi-page markup
1258 @cindex multi-page markup
1259 @cindex markup, multi-page
1260 @cindex markup text, multi-page
1261 @cindex text spread over multiple pages
1263 @funindex \markuplines
1264 @funindex markuplines
1265 @funindex \justified-lines
1266 @funindex justified-lines
1267 @funindex \wordwrap-lines
1268 @funindex wordwrap-lines
1270 Although standard markup objects are not breakable, a specific syntax
1271 makes it possible to enter lines of text that can spread over multiple
1274 @lilypond[quote,verbatim]
1277 A very long text of justified lines.
1281 Another very long paragraph.
1288 This syntax accepts a list of markups, that can be
1291 the result of a markup list command,
1295 a list of markup lists.
1298 An exhaustive list of markup list commands can be found in
1299 @ref{Text markup list commands}.
1304 @ref{Text markup list commands},
1310 @rextend{New markup list command definition}.
1312 Internals Reference:
1313 @rinternals{TextScript}.
1316 @file{scm/@/define@/-markup@/-commands@/.scm}.
1319 @funindex \markuplines
1320 @funindex markuplines
1323 @code{\markuplines}.
1330 This section presents the way fonts are handled, and how they may be
1335 * Single entry fonts::
1336 * Entire document fonts::
1339 @node Fonts explained
1340 @unnumberedsubsubsec Fonts explained
1343 @cindex fonts, explained
1344 @cindex braces, various sizes
1345 @cindex fonts, non-text in markup
1346 @cindex non-text fonts in markup
1348 @funindex font-interface
1350 Fonts are handled through several libraries. FontConfig is used to
1351 detect available fonts on the system; the selected fonts are rendered
1354 Music notation fonts can be described as a set of specific glyphs,
1355 ordered in several families. The following syntax allows various
1356 LilyPond @code{feta} non-text fonts to be used directly in markup
1359 @lilypond[quote,verbatim,relative=2]
1362 \override #'(font-encoding . fetaBraces)
1364 \override #'(font-encoding . fetaText)
1366 \override #'(font-encoding . fetaMusic)
1367 \lookup #"noteheads.s0petrucci"
1373 However, all these glyphs except the braces of various sizes contained
1374 in @code{fetaBraces} are available using the simpler syntax described
1375 in @ref{Music notation inside markup}.
1377 When using the glyphs contained in @code{fetaBraces}, the size of the
1378 brace is specified by the numerical part of the glyph name, in
1379 arbitrary units. Any integer from @code{0} to @code{575} inclusive
1380 may be specified, @code{0} giving the smallest brace. The optimum
1381 value must be determined by trial and error. These glyphs are all
1382 left braces; right braces may be obtained by rotation, see
1383 @ref{Rotating objects}.
1385 Three families of text fonts are made available: the @emph{roman}
1386 (serif) font, that defaults to New Century Schoolbook, the @emph{sans}
1387 font and the monospaced @emph{typewriter} font -- these last two
1388 families are determined by the Pango installation.
1390 Each family may include different shapes and series. The following
1391 example demonstrates the ability to select alternate families, shapes,
1392 series and sizes. The value supplied to @code{font-size} is the
1393 required change from the default size.
1395 @lilypond[quote,verbatim,relative=2]
1396 \override Score.RehearsalMark #'font-family = #'typewriter
1397 \mark \markup "Ouverture"
1398 \override Voice.TextScript #'font-shape = #'italic
1399 \override Voice.TextScript #'font-series = #'bold
1400 d2.^\markup "Allegro"
1401 \override Voice.TextScript #'font-size = #-3
1406 A similar syntax may be used in markup mode; however in this case it
1407 is preferable to use the simpler syntax explained in @ref{Selecting
1408 font and font size}:
1410 @lilypond[quote,verbatim]
1414 \override #'(font-shape . italic)
1415 \override #'(font-size . 4)
1419 \override #'(font-family . typewriter)
1421 \override #'(font-series . bold)
1425 \override #'(font-family . sans)
1432 Although it is easy to switch between preconfigured fonts, it is also
1433 possible to use other fonts, as explained in the following sections:
1434 @ref{Single entry fonts} and @ref{Entire document fonts}.
1439 @ref{The Feta font},
1440 @ref{Music notation inside markup},
1441 @ref{Selecting font and font size},
1445 @node Single entry fonts
1446 @unnumberedsubsubsec Single entry fonts
1448 Any font that is installed on the operating system and recognized by
1449 FontConfig may be used in a score, using the following syntax:
1451 @lilypond[quote,verbatim,relative=2]
1452 \override Staff.TimeSignature #'font-name = #"Bitstream Charter"
1453 \override Staff.TimeSignature #'font-size = #2
1457 \override #'(font-name . "Vera Bold")
1462 @cindex fonts, finding available
1463 @cindex finding available fonts
1464 @cindex listing available fonts
1465 @cindex available fonts, listing
1467 @funindex show-available-fonts
1469 The following command displays a list of all available fonts on the
1473 lilypond -dshow-available-fonts x
1479 @ref{Fonts explained},
1480 @ref{Entire document fonts}.
1485 @c A source file gets never installed...
1487 @c @file{lily/@/font@/-config@/-scheme@/.cc}.
1490 @node Entire document fonts
1491 @unnumberedsubsubsec Entire document fonts
1493 It is possible to change the fonts to be used as the default fonts in
1494 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1495 specifying them, in that order, as shown in the example below. For an
1496 explanation of fonts, see @ref{Fonts explained}.
1498 @cindex font families, setting
1499 @cindex fonts, changing for entire document
1501 @funindex make-pango-font-tree
1503 @lilypond[verbatim,quote]
1507 (make-pango-font-tree "Times New Roman"
1510 (/ myStaffSize 20)))
1517 \typewriter typewriter. }
1521 @c we don't do Helvetica / Courier, since GS incorrectly loads
1527 @ref{Fonts explained},
1528 @ref{Single entry fonts},
1529 @ref{Selecting font and font size},