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}.
30 @subsection Writing text
32 This section introduces different ways of adding text to a score.
34 @cindex Text, other languages
35 @warning{To write accented and special text (such as characters
36 from other languages), simply insert the characters directly into
37 the LilyPond file. The file must be saved as UTF-8. For more
38 information, see @ref{Text encoding}.}
49 @unnumberedsubsubsec Text scripts
52 @cindex text items, non-empty
53 @cindex non-empty texts
56 Simple @qq{quoted text} indications may be added to a score.
58 @lilypond[quote,verbatim,relative=2]
59 a8^"pizz." g f e a4-"scherz." f
62 This syntax is actually a shorthand; more complex text
63 formatting may be added to a note by explicitly using a
64 @code{\markup} block, as described in @ref{Formatting text}.
66 @lilypond[quote,verbatim,relative=2]
67 a8^\markup { \italic pizz. } g f e
68 a4_\markup { \tiny scherz. \bold molto } f
71 @qq{Quoted text} and @code{\markup} commands may be manually
72 placed above or below the staff; see @ref{Direction and
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]
88 @funindex \textLengthOn
90 @funindex \textLengthOff
91 @code{\textLengthOff}.
97 @ref{Formatting text},
98 @ref{Direction and placement}.
104 @rinternals{TextScript}.
109 Checking to make sure that text scripts and lyrics are within the
110 margins is a relatively large computational task. To speed up
111 processing, LilyPond does not perform such calculations by
112 default; to enable it, use
115 \override Score.PaperColumn #'keep-inside-line = ##t
120 @unnumberedsubsubsec Text spanners
122 @cindex Text spanners
124 Some performance indications, e.g., @notation{rallentando} or
125 @notation{accelerando}, are written as text and are extended over
126 multiple notes with dotted lines.
127 Such objects, called @qq{spanners}, may be created
128 from one note to another using the following syntax:
130 @lilypond[verbatim,quote,relative=2]
131 \override TextSpanner #'(bound-details left text) = "rit."
137 The string to be printed is set through
138 object properties. By default it is printed in italic characters,
139 but different formatting can be obtained using
140 @code{\markup} blocks, as described in @ref{Formatting text}.
142 @lilypond[quote,relative=2,verbatim]
143 \override TextSpanner #'(bound-details left text) =
144 \markup { \upright "rit." }
149 The line style, as well as the text string, can be defined as an
150 object property. This syntax is described in @ref{Line styles}.
152 Text spanners may be manually placed above or below the staff; see
153 @ref{Direction and placement}.
157 @funindex textSpannerUp
158 @code{\textSpannerUp},
159 @funindex textSpannerDown
160 @code{\textSpannerDown},
161 @funindex textSpannerNeutral
162 @code{\textSpannerNeutral}.
170 @ref{Direction and placement}.
176 @rinternals{TextSpanner}.
180 @unnumberedsubsubsec Text marks
182 @cindex coda on bar line
183 @cindex segno on bar line
184 @cindex fermata on bar line
185 @cindex bar lines, symbols on
188 Various text elements may be added to a score using
189 the syntax described in @ref{Rehearsal marks}:
191 @c \mark needs to be placed on a separate line (it's not
192 @c attached to an object like \markup is). -vv
194 @lilypond[verbatim,quote,relative=2]
200 This syntax makes it possible to put any text on a bar line;
201 more complex text formatting may be added using a @code{\markup}
202 block, as described in @ref{Formatting text}:
204 @lilypond[quote,verbatim,relative=1]
206 \mark \markup { \italic { colla parte } }
212 This syntax also allows to print special signs, like coda, segno
213 or fermata, by specifying the appropriate symbol name as explained in
214 @ref{Music notation inside markup}:
216 @lilypond[quote,verbatim,relative=2]
218 \mark \markup { \musicglyph #"scripts.ufermata" }
223 Such objects are only typeset above the top staff of the score; depending on
224 whether they are specified at the end or the middle of a bar, they
225 can be placed above the bar line or between notes. When specified at a
226 line break, the mark will be printed at the beginning of the next line.
228 @lilypond[quote,verbatim,relative=2]
238 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
239 {printing-marks-at-the-end-of-a-line-or-a-score.ly}
241 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
242 {aligning-marks-with-various-notation-objects.ly}
244 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
245 {printing-marks-on-every-staff.ly}
250 @ref{Rehearsal marks},
251 @ref{Formatting text},
252 @ref{Music notation inside markup},
259 @rinternals{RehearsalMark}.
263 @c To be removed when Issue 69 in the tracker gets fixed. -vv
265 If a mark is entered at the end of the last bar of the score (where
266 there is no next line), then the mark will not be printed at
270 @unnumberedsubsubsec Separate text
272 @cindex separate text
273 @cindex standalone text
274 @cindex top-level text
275 @cindex text, standalone
278 A @code{\markup} block can exist by itself, outside of any
279 any @code{\score} block, as a @qq{top-level
280 expression}. This syntax is described in @ref{File structure}.
282 @lilypond[verbatim,quote]
284 Tomorrow, and tomorrow, and tomorrow...
289 This allows printing text separately
290 from the music, which is particularly
291 useful when the input file contains
292 several music pieces, as described in
293 @ref{Multiple scores in a book}.
295 @lilypond[quote,verbatim]
300 Tomorrow, and tomorrow, and tomorrow...
307 Separate text blocks can be spread over multiple pages,
308 making it possible to print text documents or books entirely
309 within LilyPond. This feature, and the specific syntax it
310 requires, are described in @ref{Multi-page markup}.
314 @funindex \markuplines
322 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
323 {stand-alone-two-column-markup.ly}
326 Notation Reference: @ref{Formatting text},
327 @ref{File structure},
328 @ref{Multiple scores in a book},
329 @ref{Multi-page markup}.
334 Internals Reference: @rinternals{TextScript}.
337 @node Formatting text
338 @subsection Formatting text
340 This section presents basic and advanced text formatting,
341 using the @code{\markup} mode specific syntax.
344 * Text markup introduction::
345 * Selecting font and font size::
347 * Graphic notation inside markup::
348 * Music notation inside markup::
349 * Multi-page markup::
352 @node Text markup introduction
353 @unnumberedsubsubsec Text markup introduction
361 A @code{\markup} block is used to typeset text with an extensible
362 syntax called @qq{markup mode}.
364 @cindex markup expressions
365 @cindex markup syntax
367 The markup syntax is similar to LilyPond's usual syntax: a
368 @code{\markup} expression is enclosed in curly braces @code{@{
369 @dots{} @}}. A single word is regarded as a minimal expression,
370 and therefore does not need to be enclosed with braces.
372 Unlike simple @qq{quoted text} indications, @code{\markup} blocks
373 may contain nested expressions or markup commands,
374 entered using the backslash @code{\} character.
375 Such commands only affect the first following expression.
377 @lilypond[quote,verbatim,relative=2]
379 a2^\markup { poco \italic più forte }
381 d2_\markup { \italic "string. assai" }
383 b1^\markup { \bold { molto \italic agitato } }
387 @cindex special characters in markup mode
388 @cindex markup mode, special characters
389 @cindex reserved characters, printing
390 @cindex printing special characters
391 @cindex quoted text in markup mode
393 A @code{\markup} block may also contain quoted text strings.
394 Such strings are treated as minimal text expressions, and
395 therefore any markup command or special character (such as
396 @code{\} and @code{#}) will be printed verbatim without affecting
397 the formatting of the text. Double quotation marks themselves
398 may be printed by preceding them with backslashes.
400 @lilypond[quote,verbatim,relative=2]
401 a1^"\italic markup..."
402 a_\markup { \italic "... prints \"italic\" letters!" }
406 To be treated as a distinct expression, a list of words needs
407 to be enclosed with double quotes or preceded by a command.
408 The way markup expressions are defined affects how these
409 expressions will be stacked, centered and aligned; in the
410 following example, the second @code{\markup} expression is
411 treated the same as the first one:
413 @lilypond[quote,verbatim,relative=2]
414 c1^\markup { \center-column { a bbb c } }
415 c1^\markup { \center-column { a { bbb c } } }
416 c1^\markup { \center-column { a \line { bbb c } } }
417 c1^\markup { \center-column { a "bbb c" } }
420 Markups can be stored in variables. Such variables may be
421 directly attached to notes:
423 @lilypond[quote,verbatim]
424 allegro = \markup { \bold \large Allegro }
434 An exhaustive list of @code{\markup}-specific commands can be found in
435 @ref{Text markup commands}.
440 @ref{Text markup commands}.
446 @file{scm/@/markup@/.scm}.
451 Syntax errors for markup mode can be confusing.
454 @node Selecting font and font size
455 @unnumberedsubsubsec Selecting font and font size
457 @cindex font switching
462 Basic font switching is supported in markup mode:
464 @lilypond[quote,verbatim,relative=2]
467 \italic { non troppo \underline Vivo }
470 d,_\markup { \italic quasi \smallCaps Tromba }
481 The size of the characters can also be altered in different ways:
484 the font size can be set to predefined standard sizes,
487 the font size can be set to an absolute value,
490 the font size can also be changed relatively to its previous value.
494 The following example demonstrates these three methods:
496 @lilypond[quote,verbatim,relative=1]
503 \fontsize #5 Sinfonia
510 \magnify #0.6 { e sentimento } )
520 Text may be printed as subscript or superscript. By default
521 these are printed in a smaller size, but a normal size can be used as well:
523 @lilypond[quote,verbatim]
526 \line { 1 \super st movement }
527 \line { 1 \normal-size-super st movement
528 \sub { (part two) } }
533 @cindex font families
535 The markup mode provides an easy way to select alternate
536 font families. The default serif font, of roman type, is
537 automatically selected unless specified otherwise; on the
538 last line of the following example, there is no difference
539 between the first and the second word.
541 @lilypond[quote,verbatim]
544 \line { Act \number 1 }
545 \line { \sans { Scene I. } }
546 \line { \typewriter { Verona. An open place. } }
547 \line { Enter \roman Valentine and Proteus. }
553 Some of these font families, used for specific items
554 such as numbers or dynamics, do not provide all
555 characters, as mentioned in @ref{New dynamic marks} and
556 @ref{Manual repeat marks}.
558 @c \concat is actually documented in Align (it is not
559 @c a font-switching command). But we need it here. -vv
561 When used inside a word, some font-switching or formatting
562 commands may produce an unwanted blank space. This can
563 easily be solved by concatenating the text elements together:
565 @lilypond[quote,verbatim]
569 \concat { 1 \super st }
573 \concat { \dynamic p , }
574 \italic { con dolce espressione }
580 An exhaustive list of font switching, and custom font usage
581 commands can be found in @ref{Font}.
583 Defining custom font sets is also possible, as explained in
594 @funindex \normalsize
610 @ref{New dynamic marks},
611 @ref{Manual repeat marks},
618 @rinternals{TextScript}.
621 @file{scm/@/define@/-markup@/-commands@/.scm}.
625 @unnumberedsubsubsec Text alignment
627 @cindex text, aligning
628 @cindex aligning text
630 This subsection discusses how to place text in markup mode.
631 Markup objects can also be moved as a whole, using the syntax
632 described in @rlearning{Moving objects}.
634 @c Padding commands should be mentioned on this page, but
635 @c most of these require \box to be more clearly illustrated. -vv
637 @cindex text, horizontal alignment
638 @cindex horizontal text alignment
639 @funindex \left-align
640 @funindex \center-align
641 @funindex \right-align
643 Markup objects may be aligned in different ways. By default,
644 a text indication is aligned on its left edge: in the following
645 example, there is no difference
646 between the first and the second markup.
648 @lilypond[quote,verbatim,relative=2]
651 d-\markup { \left-align poco }
653 d-\markup { \center-align { poco } }
655 d-\markup { \right-align poco }
660 Horizontal alignment may be fine-tuned
661 using a numeric value:
663 @lilypond[quote,verbatim,relative=2]
664 a1-\markup { \halign #-1 poco }
666 a,-\markup { \halign #0 poco }
668 a,-\markup { \halign #0.5 poco }
670 a,-\markup { \halign #2 poco }
674 Some objects may have alignment procedures of their own,
675 and therefore are not affected by these commands. It is
676 possible to move such markup objects as a whole, as shown
677 for instance in @ref{Text marks}.
679 @cindex text, vertical alignment
680 @cindex vertical text alignment
684 Vertical alignment is a bit more complex. As stated above,
685 markup objects can be moved as a whole; however, it is also
686 possible to move specific elements inside a markup block.
687 In this case, the element to be moved needs to be preceded
688 with an @emph{anchor point}, that can be another markup element
689 or an invisible object. The following example demonstrates these
690 two possibilities; the last markup in this example has no anchor
691 point, and therefore is not moved.
693 @lilypond[quote,verbatim,relative=1]
696 \raise #2 { Scène 1 }
701 \lower #4 \bold { Très modéré }
705 \raise #4 \italic { Une forêt. }
710 @funindex \general-align
712 @funindex \translate-scaled
714 Some commands can affect both the horizontal and vertical
715 alignment of text objects in markup mode. Any object
716 affected by these commands must be preceded with an
719 @lilypond[quote,verbatim,relative=1]
722 \translate #'(-1 . 2) "Scène 1"
727 \general-align #Y #3.2 \bold "Très modéré"
732 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
738 @funindex \center-column
740 @cindex multi-line markup
741 @cindex multi-line text
742 @cindex columns, text
744 A markup object may include several lines of text.
745 In the following example, each element or expression
746 is placed on its own line, either left-aligned or centered:
748 @lilypond[quote,verbatim]
766 @cindex centering text on the page
768 Similarly, a list of elements or expressions may be
769 spread to fill the entire horizontal line width (if there
770 is only one element, it will be centered on the page).
771 These expressions can, in turn, include multi-line text
772 or any other markup expression:
774 @lilypond[quote,verbatim]
777 \line { William S. Gilbert }
779 \huge \smallCaps "The Mikado"
781 \smallCaps "The Town of Titipu"
783 \line { Sir Arthur Sullivan }
794 @cindex wordwrapped text
795 @cindex justified text
797 Long text indications can also be automatically wrapped
798 accordingly to the given line width. These will be
799 either left-aligned or justified, as shown in
800 the following example.
802 @lilypond[quote,verbatim]
805 \line \smallCaps { La vida breve }
806 \line \bold { Acto I }
808 (La escena representa el corral de una casa de
809 gitanos en el AlbaicÃn de Granada. Al fondo una
810 puerta por la que se ve el negro interior de
811 una Fragua, iluminado por los rojos resplandores
816 \line \bold { Acto II }
817 \override #'(line-width . 50)
819 (Calle de Granada. Fachada de la casa de Carmela
820 y su hermano Manuel con grandes ventanas abiertas
821 a través de las que se ve el patio
822 donde se celebra una alegre fiesta)
828 An exhaustive list of text alignment commands
829 can be found in @ref{Align}.
834 @rlearning{Moving objects}.
843 Internals Reference: @rinternals{TextScript}.
846 @file{scm/@/define@/-markup@/-commands@/.scm}.
849 @node Graphic notation inside markup
850 @unnumberedsubsubsec Graphic notation inside markup
852 @cindex graphics, embedding
853 @cindex drawing graphic objects
855 Various graphic objects may be added to a score,
856 using markup commands.
860 @funindex \rounded-box
864 @cindex decorating text
867 Some markup commands allow decoration of text elements
868 with graphics, as demonstrated in the following example.
870 @lilypond[quote,verbatim]
879 \bracket "1866 - 1925"
882 \rounded-box \bold Prelude
887 @funindex \pad-markup
889 @funindex \pad-to-box
890 @funindex \pad-around
892 @cindex padding around text
895 Some commands may require an increase in the padding around
896 the text; this is achieved with some markup commands
897 exhaustively described in @ref{Align}.
899 @lilypond[quote,verbatim]
902 \box "Charles Ives (1874 - 1954)"
904 \box \pad-markup #2 "THE UNANSWERED QUESTION"
905 \box \pad-x #8 "A Cosmic Landscape"
912 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
913 \bold "Largo to Presto"
916 "String quartet keeps very even time,
917 Flute quartet keeps very uneven time."
922 @funindex \draw-circle
923 @funindex \filled-box
926 @funindex \arrow-head
928 @cindex graphic notation
929 @cindex symbols, non-musical
931 Other graphic elements or symbols may be printed
932 without requiring any text. As with any markup
933 expression, such objects can be combined.
935 @lilypond[quote,verbatim]
938 \draw-circle #4 #0.4 ##f
939 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
946 \arrow-head #Y #DOWN ##f
952 @funindex \postscript
954 @cindex embedded graphics
955 @cindex images, embedding
956 @cindex graphics, embedding
959 Advanced graphic features include the ability to
960 include external image files converted to the
961 Encapsulated PostScript format (@emph{eps}), or
962 to directly embed graphics into the input file,
963 using native PostScript code. In such a case, it
964 may be useful to explicitly specify the size of the
965 drawing, as demonstrated below:
967 @lilypond[quote,verbatim,relative=1]
970 \epsfile #X #10 #"./context-example.eps"
971 \with-dimensions #'(0 . 6) #'(0 . 10)
987 An exhaustive list of graphics-specific commands
988 can be found in @ref{Graphic}.
994 @ref{Editorial annotations}.
999 Internals Reference: @rinternals{TextScript}.
1002 @file{scm/@/define@/-markup@/-commands@/.scm},
1003 @file{scm/@/stencil@/.scm}.
1006 @node Music notation inside markup
1007 @unnumberedsubsubsec Music notation inside markup
1009 Various musical notation elements may be added
1010 to a score, inside a markup object.
1012 Notes and accidentals can be entered using markup
1015 @lilypond[quote,verbatim,relative=2]
1019 \note-by-number #1 #1 #1.5
1022 \natural \semiflat \flat
1023 \sesquiflat \doubleflat
1027 \natural \semisharp \sharp
1028 \sesquisharp \doublesharp
1033 Other notation objects may also be printed
1036 @lilypond[quote,verbatim,relative=1]
1043 fis_\markup { \dynamic rf }
1054 More generally, any available musical symbol may be
1055 included separately in a markup object, as demonstrated
1056 below; an exhaustive list of these symbols and their
1057 names can be found in @ref{The Feta font}.
1059 @lilypond[quote,verbatim,relative=2]
1061 c'^\markup { \musicglyph #"eight" }
1063 c,8._\markup { \musicglyph #"clefs.G_change" }
1065 c2^\markup { \musicglyph #"timesig.neomensural94" }
1069 Another way of printing non-text glyphs is described in
1070 @ref{Fonts explained}. This is useful for printing braces of
1073 The markup mode also supports diagrams for specific
1076 @lilypond[quote,verbatim,relative=2]
1078 \fret-diagram-terse #"x;x;o;2;3;2;"
1081 \harp-pedal #"^-v|--ov^"
1086 \musicglyph #"accordion.accDiscant"
1088 \raise #0.5 \musicglyph #"accordion.accDot"
1089 \raise #1.5 \musicglyph #"accordion.accDot"
1093 @c The accordion diagram is actually taken from a snippet.
1096 Such diagrams are documented in @ref{Instrument Specific Markup}.
1098 A whole score can even be nested inside a markup object.
1099 In such a case, the nested @code{\score} block must
1100 contain a @code{\layout} block, as demonstrated here:
1102 @lilypond[quote,verbatim,relative=1]
1105 \relative c' { c4 d e f }
1113 An exhaustive list of music notation related commands can be
1114 found in @ref{Music}.
1120 @ref{The Feta font},
1121 @ref{Fonts explained}.
1126 Internals Reference: @rinternals{TextScript}.
1129 @file{scm/@/define@/-markup@/-commands@/.scm},
1130 @file{scm/@/fret@/-diagrams@/.scm},
1131 @file{scm/@/harp@/-pedals@/.scm}.
1134 @node Multi-page markup
1135 @unnumberedsubsubsec Multi-page markup
1137 Although standard markup objects are not breakable, a
1138 specific syntax makes it possible to enter lines of text that can
1139 spread over multiple pages:
1141 @lilypond[quote,verbatim]
1144 A very long text of justified lines.
1148 Another very long paragraph.
1155 This syntax accepts a list of markups, that can be
1158 the result of a markup list command,
1162 a list of markup lists.
1165 An exhaustive list of markup list commands can be found in
1166 @ref{Text markup list commands}.
1171 @ref{Text markup list commands},
1172 @ref{New markup list command definition}.
1177 Internals Reference: @rinternals{TextScript}.
1180 @file{scm/@/define@/-markup@/-commands@/.scm}.
1184 @funindex \markuplines
1185 @code{\markuplines}.
1192 This section presents the way fonts are handled,
1193 and how they may be changed in scores.
1197 * Single entry fonts::
1198 * Entire document fonts::
1201 @node Fonts explained
1202 @unnumberedsubsubsec Fonts explained
1205 @cindex fonts, explained
1206 @cindex braces, various sizes
1207 @funindex font-interface
1209 Fonts are handled through several libraries.
1210 FontConfig is used to detect available fonts on the system;
1211 the selected fonts are rendered using Pango.
1213 Music notation fonts can be described as a set of
1214 specific glyphs, ordered in several families.
1215 The following syntax allows various LilyPond @code{feta} non-text
1216 fonts to be used directly in markup mode:
1218 @lilypond[quote,verbatim,relative=2]
1221 \override #'(font-encoding . fetaBraces)
1223 \override #'(font-encoding . fetaNumber)
1225 \override #'(font-encoding . fetaDynamic)
1227 \override #'(font-encoding . fetaMusic)
1228 \lookup #"noteheads.s0petrucci"
1234 However, all these glyphs except the braces of various sizes
1235 contained in @code{fetaBraces} are available using the
1236 simpler syntax described in @ref{Music notation inside markup}.
1238 When using the glyphs contained in @code{fetaBraces}, the size of
1239 the brace is specified by the numerical part of the glyph name, in
1240 arbitrary units. Any integer from @code{0} to @code{575} inclusive
1241 may be specified, @code{0} giving the smallest brace. The optimum
1242 value must be determined by trial and error. These glyphs are all
1243 left braces; right braces may be obtained by rotation, see
1244 @ref{Rotating objects}.
1246 Three families of text fonts are made available: the
1247 @emph{roman} (serif) font, that defaults to New Century
1248 Schoolbook, the @emph{sans} font and the monospaced
1249 @emph{typewriter} font -- these last two families are
1250 determined by the Pango installation.
1252 Each family may include different shapes and series.
1253 The following example demonstrates the ability to select
1254 alternate families, shapes, series and sizes. The value
1255 supplied to @code{font-size} is the required change from the
1258 @lilypond[quote,verbatim,relative=2]
1259 \override Score.RehearsalMark #'font-family = #'typewriter
1260 \mark \markup "Ouverture"
1261 \override Voice.TextScript #'font-shape = #'italic
1262 \override Voice.TextScript #'font-series = #'bold
1263 d2.^\markup "Allegro"
1264 \override Voice.TextScript #'font-size = #-3
1269 A similar syntax may be used in markup mode, however in this case
1270 it is preferable to use the simpler syntax explained in
1271 @ref{Selecting font and font size}:
1273 @lilypond[quote,verbatim]
1277 \override #'(font-shape . italic)
1278 \override #'(font-size . 4)
1282 \override #'(font-family . typewriter)
1284 \override #'(font-series . bold)
1288 \override #'(font-family . sans)
1295 Although it is easy to switch between preconfigured fonts,
1296 it is also possible to use other fonts, as explained in the
1297 following sections: @ref{Single entry fonts} and
1298 @ref{Entire document fonts}.
1303 @ref{The Feta font},
1304 @ref{Music notation inside markup},
1305 @ref{Selecting font and font size},
1309 @node Single entry fonts
1310 @unnumberedsubsubsec Single entry fonts
1312 Any font that is installed on the operating system and recognized
1313 by FontConfig may be used in a score, using the following syntax:
1315 @lilypond[quote,verbatim,relative=2]
1316 \override Staff.TimeSignature #'font-name = #"Charter"
1317 \override Staff.TimeSignature #'font-size = #2
1321 \override #'(font-name . "Vera Bold")
1326 @funindex show-available-fonts
1328 The following command displays a list of all available fonts
1329 on the operating system:
1332 lilypond -dshow-available-fonts x
1336 The last argument of the command can be anything, but has to be
1342 @ref{Fonts explained},
1343 @ref{Entire document fonts}.
1349 @file{lily/@/font@/-config@/-scheme@/.cc}.
1352 @node Entire document fonts
1353 @unnumberedsubsubsec Entire document fonts
1355 It is possible to change the fonts to be used as the default fonts in
1356 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1357 specifying them, in that order, as shown in the example below. For an
1358 explanation of fonts, see @ref{Fonts explained}.
1360 @cindex font families, setting
1361 @funindex make-pango-font-tree
1363 @lilypond[verbatim,quote]
1367 (make-pango-font-tree "Times New Roman"
1370 (/ myStaffSize 20)))
1377 \typewriter typewriter. }
1381 @c we don't do Helvetica / Courier, since GS incorrectly loads
1387 @ref{Fonts explained},
1388 @ref{Single entry fonts},
1389 @ref{Selecting font and font size},