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}.
29 @cindex Text, other languages
30 @warning{To write accented and special text (such as characters
31 from other languages), simply insert the characters directly into
32 the LilyPond file. The file must be saved as UTF-8. For more
33 information, see @ref{Text encoding}.}
36 @subsection Writing text
38 This section introduces different ways of adding text to a score.
49 @unnumberedsubsubsec Text scripts
52 @cindex text items, non-empty
53 @cindex non-empty texts
56 Simple @qq{quoted text} indications may be added
57 to a score, as demonstrated in the following example.
58 Such indications may be manually placed
59 above or below the staff, using the
60 syntax described in @ref{Direction and
63 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
64 d8^"pizz." e f g a4-"scherz." f
67 This syntax is actually a shorthand; more complex text
68 formatting may be added to a note by explicitly using a
69 @code{\markup} block, as described in @ref{Formatting text}.
71 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
72 d8^\markup { \italic pizz. } e f g
73 a4_\markup { \tiny scherz. \bold molto } f
76 By default, text indications do not influence the note spacing.
77 However, their widths can be taken into account:
78 in the following example, the first text string does not affect
79 spacing, whereas the second one does.
81 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
89 @funindex \textLengthOn
91 @funindex \textLengthOff
98 @ref{Formatting text},
99 @ref{Direction and placement}.
105 @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,ragged-right,fragment,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,ragged-right,fragment,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}.
154 @funindex textSpannerUp
155 @code{\textSpannerUp},
156 @funindex textSpannerDown
157 @code{\textSpannerDown},
158 @funindex textSpannerNeutral
159 @code{\textSpannerNeutral}
171 @rinternals{TextSpanner}.
175 @unnumberedsubsubsec Text marks
177 @cindex coda on bar line
178 @cindex segno on bar line
179 @cindex fermata on bar line
180 @cindex bar lines, symbols on
183 Various text elements may be added to a score using
184 the syntax described in @ref{Rehearsal marks}:
186 @c \mark needs to be placed on a separate line (it's not
187 @c attached to an object like \markup is). -vv
189 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
195 This syntax makes it possible to put any text on a bar line;
196 more complex text formatting may be added using a @code{\markup}
197 block, as described in @ref{Formatting text}:
199 @lilypond[fragment,quote,ragged-right,verbatim,relative=1]
201 \mark \markup { \italic { colla parte } }
207 This syntax also allows to print special signs, like coda, segno
208 or fermata, by specifying the appropriate symbol name as explained in
209 @ref{Music notation inside markup}:
211 @lilypond[fragment,quote,ragged-right,verbatim,relative=1]
213 \mark \markup { \musicglyph #"scripts.ufermata" }
218 Such objects are only typeset above the top staff of the score; depending on
219 whether they are specified at the end or the middle of a bar, they
220 can be placed above the bar line or between notes. When specified at a
221 line break, the mark will be printed at the beginning of the next line.
223 @lilypond[fragment,quote,ragged-right,verbatim,relative=2]
233 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
234 {printing-marks-at-the-end-of-a-line-or-a-score.ly}
236 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
237 {aligning-marks-with-various-notation-objects.ly}
239 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
240 {printing-marks-on-every-staff.ly}
245 @ref{Rehearsal marks},
246 @ref{Formatting text},
247 @ref{Music notation inside markup},
254 @rinternals{RehearsalMark}.
257 @c To be removed when Issue 69 in the tracker gets fixed. -vv
259 If a mark is entered at the end of the last bar of the score (where
260 there is no next line), then the mark will not be printed at
264 @unnumberedsubsubsec Separate text
266 @cindex separate text
267 @cindex standalone text
268 @cindex top-level text
269 @cindex text, standalone
272 A @code{\markup} block can exist by itself, outside of any
273 any @code{\score} block, as a @qq{top-level
274 expression}. This syntax is described in @ref{File structure}.
276 @lilypond[verbatim,quote]
278 Tomorrow, and tomorrow, and tomorrow...
283 This allows printing text separately
284 from the music, which is particularly
285 useful when the input file contains
286 several music pieces, as described in
287 @ref{Multiple scores in a book}.
289 @lilypond[quote,ragged-right,verbatim]
294 Tomorrow, and tomorrow, and tomorrow...
301 Using a specific syntax, text blocks can be spread
302 over multiple pages, making it possible to print
303 text documents or books (and therefore to
304 use LilyPond as a word processor). This syntax is described in
305 @ref{Multi-page markup}.
310 @funindex \markuplines
316 TODO: add convenient snippets in input/new -vv
321 Notation Reference: @ref{Formatting text},
322 @ref{File structure},
323 @ref{Multiple scores in a book},
324 @ref{Multi-page markup}.
329 Internals Reference: @rinternals{TextScript}.
332 @node Formatting text
333 @subsection Formatting text
335 This section presents basic and advanced text formatting,
336 using the @code{\markup} mode specific syntax.
339 * Text markup introduction::
340 * Selecting font and font size::
342 * Graphic notation inside markup::
343 * Music notation inside markup::
344 * Multi-page markup::
347 @node Text markup introduction
348 @unnumberedsubsubsec Text markup introduction
356 A @code{\markup} block is used to typeset text with an extensible
357 specific syntax called @qq{markup mode}.
359 @cindex markup expressions
360 @cindex markup syntax
362 The markup syntax is similar to LilyPond's usual syntax: a
363 @code{\markup} expression is enclosed in curly braces @code{@{
364 @dots{} @}}. A single word is regarded as a minimal expression,
365 and therefore does not need to be enclosed with braces.
367 Unlike simple @qq{quoted text} indications, @code{\markup} blocks
368 may contain nested expressions or specific commands,
369 entered using the backslash @code{\} character.
370 Such commands only affect the first following expression.
372 @lilypond[quote,verbatim,fragment,relative=1]
374 a2^\markup { poco \italic più forte }
376 d2_\markup { \italic "string. assai" }
378 b1^\markup { \bold { molto \italic agitato } }
382 @cindex special characters in markup mode
383 @cindex markup mode, special characters
384 @cindex reserved characters, printing
385 @cindex printing special characters
386 @cindex quoted text in markup mode
388 A @code{\markup} block may also contain quoted text strings.
389 Such strings are treated as minimal text expressions, and
390 therefore any markup command or special character (such as
391 @code{\} and @code{#}) will be printed verbatim without affecting
392 the formatting of the text. Double quotation marks themselves
393 may be printed by preceding them with backslashes.
395 @lilypond[quote,verbatim,fragment,relative=1]
396 d1^"\italic markup..."
397 d_\markup { \italic "... prints \"italic\" letters!" }
401 To be treated as a distinct expression, a list of words needs
402 to be enclosed with double quotes or preceded by a command.
403 The way markup expressions are defined affects how these
404 expressions will be stacked, centered and aligned; in the
405 following example, the second @code{\markup} expression is
406 not treated differently from the first one :
408 @lilypond[quote,verbatim,fragment,relative=1]
409 c1^\markup { \center-column { a bbb c } }
410 c1^\markup { \center-column { a { bbb c } } }
411 c1^\markup { \center-column { a \line { bbb c } } }
412 c1^\markup { \center-column { a "bbb c" } }
415 Markups can be stored in variables. Such variables may be
416 directly attached to notes:
418 @lilypond[quote,verbatim]
419 allegro = \markup { \bold \large Allegro }
429 An exhaustive list of @code{\markup}-specific commands can be found in
430 @ref{Text markup commands}.
436 @ref{Text markup commands}.
442 @file{scm/@/markup@/.scm}.
447 Syntax errors for markup mode can be confusing.
450 @node Selecting font and font size
451 @unnumberedsubsubsec Selecting font and font size
453 @cindex font switching
458 Basic font switching is supported in markup mode:
460 @lilypond[quote,verbatim,relative=2]
463 \italic { non troppo \underline Vivo }
466 d,_\markup { \italic quasi \smallCaps Tromba }
478 The size of the characters can also be altered in different ways:
481 the font size can be set to predefined standard sizes,
484 the font size can be set to an absolute value,
487 the font size can also be changed relatively to its previous value.
491 The following example demonstrates these three methods:
493 @lilypond[quote,verbatim,relative=2]
500 \fontsize #5 Sinfonia
507 \magnify #0.6 { e sentimento } )
517 Text may be printed as subscript or superscript. By default
518 these are printed in a smaller size, but a normal size can be used as well:
520 @lilypond[quote,verbatim]
523 \line { 1 \super st movement }
524 \line { 1 \normal-size-super st movement
525 \sub { (part two) } }
530 @cindex font families
532 The markup mode provides an easy way to select alternate
533 font families. The default serif font, of roman type, is
534 automatically selected unless specified otherwise; on the
535 last line of the following example, there is no difference
536 between the first and the second word.
538 @lilypond[quote,verbatim]
541 \line { Act \number 1 }
542 \line { \sans { Scene I. } }
543 \line { \typewriter { Verona. An open place. } }
544 \line { Enter \roman Valentine and Proteus. }
550 Some of these font families, used for specific items
551 such as numbers or dynamics, do not provide all
552 characters, as mentioned in @ref{New dynamic marks} and
553 @ref{Manual repeat marks}.
555 @c \concat is actually documented in Align (it is not
556 @c a font-switching command). But we need it here. -vv
558 When used inside a word, some font-switching or formatting
559 commands may produce an unwanted blank space. This can
560 easily be solved by concatenating the text elements together:
562 @lilypond[quote,verbatim]
566 \concat { 1 \super st }
570 \concat { \dynamic p , }
571 \italic { con dolce espressione }
577 An exhaustive list of font-switching, font-size
578 and font-families related commands can be found in @ref{Font}.
580 Defining custom font sets is also possible, as explained in
588 @funindex \normalsize
605 @ref{New dynamic marks},
606 @ref{Manual repeat marks},
613 @rinternals{TextScript}.
616 @file{scm/@/define@/-markup@/-commands@/.scm}.
620 @unnumberedsubsubsec Text alignment
622 @cindex text, aligning
623 @cindex aligning text
625 This subsection discusses how to place text in markup mode,
626 inside a @code{\markup} block. Markup objects can also
627 be moved as a whole, using the syntax described in
628 @rlearning{Moving objects}.
630 @c Padding commands should be mentioned on this page, but
631 @c most of these require \box to be more clearly illustrated. -vv
633 @cindex text, horizontal alignment
634 @cindex horizontal text alignment
635 @funindex \left-align
636 @funindex \center-align
637 @funindex \right-align
639 Markup objects may be aligned in different ways. By default,
640 a text indication is aligned on its left edge: in the following
641 example, there is no difference
642 between the first and the second markup.
644 @lilypond[quote,verbatim,fragment,relative=1]
647 a,-\markup { \left-align poco }
649 a,-\markup { \center-align { poco } }
651 a,-\markup { \right-align poco }
656 Horizontal alignment may be fine-tuned
657 using a numeric value:
659 @lilypond[quote,verbatim,fragment,relative=1]
660 a1-\markup { \halign #-1 poco }
662 a,-\markup { \halign #0 poco }
664 a,-\markup { \halign #0.5 poco }
666 a,-\markup { \halign #2 poco }
670 Some objects may have alignment procedures of their own,
671 and therefore are not affected by these commands. It is
672 possible to move such markup objects as a whole, as shown
673 for instance in @ref{Text marks},
675 @cindex text, vertical alignment
676 @cindex vertical text alignment
680 Vertical alignment is a bit more complex. As stated above,
681 markup objects can be moved as a whole; however, it is also
682 possible to move specific elements inside a markup block.
683 In this case, the element to be moved needs to be preceded
684 with an @emph{anchor point}, that can be another markup element
685 or an invisible object. The following example demonstrates these
686 two possibilities; the last markup in this example has no anchor
687 point, and therefore is not moved.
689 @lilypond[quote,verbatim,fragment,relative=1]
692 \raise #2 { Scène 1 }
697 \lower #4 \bold { Très modéré }
701 \raise #4 \italic { Une forêt. }
706 @funindex \general-align
708 @funindex \translate-scaled
710 Some commands can affect both the horizontal and vertical
711 alignment of text objects in markup mode. Any object
712 affected by these commands must be preceded with an
715 @lilypond[quote,verbatim,fragment,relative=1]
718 \translate #'(-1 . 2) "Scène 1"
723 \general-align #Y #3.2 \bold "Très modéré"
728 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
734 @funindex \center-column
736 @cindex multi-line markup
737 @cindex multi-line text
738 @cindex columns, text
740 A markup object may include several lines of text.
741 In the following example, each element or expression
742 is placed on its own line, either left-aligned or centered:
744 @lilypond[quote,verbatim]
762 @cindex centering text on the page
764 Similarly, a list of elements or expressions may be
765 spread to fill the entire horizontal line width (if there
766 is only one element, it will be centered on the page).
767 These expressions can, in turn, include multi-line text
768 or any other markup expression:
770 @lilypond[quote,verbatim]
773 \line { William S. Gilbert }
775 \huge \smallCaps "The Mikado"
777 \smallCaps "The Town of Titipu"
779 \line { Sir Arthur Sullivan }
790 @cindex wordwrapped text
791 @cindex justified text
793 Long text indications can also be automatically wrapped
794 accordingly to the given line width. These will be
795 either left-aligned or justified, as shown in
796 the following example.
798 @lilypond[quote,verbatim]
801 \line \smallCaps { La vida breve }
802 \line \bold { Acto I }
804 (La escena representa el corral de una casa de
805 gitanos en el AlbaicÃn de Granada. Al fondo una
806 puerta por la que se ve el negro interior de
807 una Fragua, iluminado por los rojos resplandores
812 \line \bold { Acto II }
813 \override #'(line-width . 50)
815 (Calle de Granada. Fachada de la casa de Carmela
816 y su hermano Manuel con grandes ventanas abiertas
817 a través de las que se ve el patio
818 donde se celebra una alegre fiesta)
824 An exhaustive list of text alignment commands
825 can be found in @ref{Align}.
829 @rlearning{Moving objects}.
838 Internals Reference: @rinternals{TextScript}.
841 @file{scm/@/define@/-markup@/-commands@/.scm}.
844 @node Graphic notation inside markup
845 @unnumberedsubsubsec Graphic notation inside markup
847 @cindex graphics, embedding
848 @cindex drawing graphic objects
850 Various graphic objects may be added to a score,
851 using specific markup commands.
855 @funindex \rounded-box
859 @cindex decorating text
862 Some markup commands allow decoration of text elements
863 with graphics, as demonstrated in the following example.
865 @lilypond[quote,verbatim]
874 \bracket "1866 - 1925"
877 \rounded-box \bold Prelude
882 @funindex \pad-markup
884 @funindex \pad-to-box
885 @funindex \pad-around
887 @cindex padding around text
890 Some commands may require an increase in the padding around
891 the text; this is achieved with some specific commands
892 exhaustively described in @ref{Align}.
894 @lilypond[quote,verbatim]
897 \box "Charles Ives (1874 - 1954)"
899 \box \pad-markup #2 "THE UNANSWERED QUESTION"
900 \box \pad-x #8 "A Cosmic Landscape"
907 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
908 \bold "Largo to Presto"
911 "String quartet keeps very even time,
912 Flute quartet keeps very uneven time."
917 @funindex \draw-circle
918 @funindex \filled-box
921 @funindex \arrow-head
923 @cindex graphic notation
924 @cindex symbols, non-musical
926 Other graphic elements or symbols may be printed
927 without requiring any text. As with any markup
928 expression, such objects can be combined.
930 @lilypond[quote,verbatim]
933 \draw-circle #4 #0.4 ##f
934 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
941 \arrow-head #Y #DOWN ##f
947 @funindex \postscript
949 @cindex embedded graphics
950 @cindex images, embedding
951 @cindex graphics, embedding
954 Advanced graphic features include the ability to
955 include external image files converted to the
956 Encapsulated PostScript format (@emph{eps}), or
957 to directly embed graphics into the input file,
958 using native PostScript code. In such a case, it
959 may be useful to explicitely specify the size of the
960 drawing, as demonstrated below:
962 @lilypond[quote,verbatim,fragment,relative=1]
965 \epsfile #X #10 #"./context-example.eps"
966 \with-dimensions #'(0 . 6) #'(0 . 10)
982 An exhaustive list of graphics-specific commands
983 can be found in @ref{Graphic}.
988 @ref{Editorial annotations}.
993 Internals Reference: @rinternals{TextScript}.
996 @file{scm/@/define@/-markup@/-commands@/.scm},
997 @file{scm/@/stencil@/.scm}.
999 @node Music notation inside markup
1000 @unnumberedsubsubsec Music notation inside markup
1002 Various musical notation elements may be added
1003 to a score, inside a markup object.
1005 Notes and accidentals can be entered using specific
1008 @lilypond[quote,verbatim,fragment,relative=2]
1012 \note-by-number #1 #1 #1.5
1015 \natural \semiflat \flat
1016 \sesquiflat \doubleflat
1020 \natural \semisharp \sharp
1021 \sesquisharp \doublesharp
1026 Other notation objects may also be printed
1029 @lilypond[quote,verbatim,fragment,relative=1]
1036 fis_\markup { \dynamic rf }
1047 More generally, any available musical symbol may be
1048 included separately in a markup object, as demonstrated
1049 below; an exhaustive list of these symbols and their
1050 names can be found in @ref{The Feta font}.
1052 @lilypond[quote,verbatim,fragment,relative=2]
1054 c'^\markup { \musicglyph #"eight" }
1056 c,8._\markup { \musicglyph #"clefs.G_change" }
1058 c2^\markup { \musicglyph #"timesig.neomensural94" }
1060 @c TODO: add \lookup here? -vv
1063 Another way of printing non-text glyphs is described
1064 in @ref{Fonts explained}.
1066 The markup mode also supports diagrams for specific
1069 @lilypond[quote,verbatim,fragment,relative=2]
1071 \fret-diagram-terse #"x;x;o;2;3;2;"
1074 \harp-pedal #"^-v|--ov^"
1079 \musicglyph #"accordion.accDiscant"
1081 \raise #0.5 \musicglyph #"accordion.accDot"
1082 \raise #1.5 \musicglyph #"accordion.accDot"
1086 @c The accordion diagram is actually taken from a snippet.
1089 Such diagrams are documented in @ref{Instrument Specific Markup}.
1091 A whole score can even be nested inside a markup object.
1092 In such a case, the nested @code{\score} block must
1093 contain a @code{\layout} block, as demonstrated here:
1095 @lilypond[quote,verbatim,fragment,relative=1]
1098 \relative { c4 d e f }
1106 An exhaustive list of music notation related commands can be
1107 found in @ref{Music}.
1112 @ref{The Feta font},
1113 @ref{Fonts explained}.
1118 Internals Reference: @rinternals{TextScript}.
1121 @file{scm/@/define@/-markup@/-commands@/.scm},
1122 @file{scm/@/fret@/-diagrams@/.scm},
1123 @file{scm/@/harp@/-pedals@/.scm}.
1125 @node Multi-page markup
1126 @unnumberedsubsubsec Multi-page markup
1128 Although standard markup objects are not breakable, a
1129 specific syntax allows to enter lines of text that can
1130 spread over multiple pages:
1132 @lilypond[quote,verbatim]
1135 A very long text of justified lines.
1139 An other very long paragraph.
1146 This specific syntax accepts a list of markups, that can be
1149 the result of a markup list command,
1153 a list of markup lists.
1156 An exhaustive list of markup list commands can be found in
1157 @ref{Text markup list commands}.
1161 @ref{Text markup list commands},
1162 @ref{New markup list command definition}.
1167 Internals Reference: @rinternals{TextScript}.
1170 @file{scm/@/define@/-markup@/-commands@/.scm}.
1173 @funindex \markuplines
1180 This section presents the way fonts are handled,
1181 and how they may be changed in scores.
1185 * Single entry fonts::
1186 * Entire document fonts::
1189 @node Fonts explained
1190 @unnumberedsubsubsec Fonts explained
1193 @cindex fonts, explained
1194 @funindex font-interface
1196 Fonts are handled through several libraries.
1197 FontConfig is used to detect available fonts on the system;
1198 the selected fonts are rendered using Pango.
1200 Music notation fonts can be described as a set of
1201 specific glyphs, ordered in several families.
1202 The following syntax allows to directly use various
1203 LilyPond @code{feta} non-text fonts in markup mode:
1205 @lilypond[quote,verbatim,fragment,relative=2]
1208 \override #'(font-encoding . fetaBraces)
1210 \override #'(font-encoding . fetaNumber)
1212 \override #'(font-encoding . fetaDynamic)
1214 \override #'(font-encoding . fetaMusic)
1215 \lookup #"noteheads.s0petrucci"
1221 A simpler, but more limited syntax is also described in
1222 @ref{Music notation inside markup}.
1224 Three families of text fonts are made available: the
1225 @emph{roman} (serif) font, that defaults to New Century
1226 Schoolbook, the @emph{sans} font and the monospaced
1227 @emph{typewriter} font -- these last two families are
1228 determined by the Pango installation.
1230 Each family may include different shapes and series.
1231 The following example demonstrates the ability to select
1232 alternate families, shapes, series and sizes:
1234 @lilypond[quote,verbatim,fragment,relative=2]
1235 \override Score.RehearsalMark #'font-family = #'typewriter
1236 \mark \markup "Ouverture"
1238 \override Voice.TextScript #'font-shape = #'italic
1239 \override Voice.TextScript #'font-series = #'bold
1240 d'2.^\markup "Allegro"
1245 A similar syntax may be used in markup mode, however in this case
1246 it is preferable to use the simpler syntax explained in
1247 @ref{Selecting font and font size}:
1249 @lilypond[quote,verbatim]
1253 \override #'(font-shape . italic)
1254 \override #'(font-size . 4)
1258 \override #'(font-family . typewriter)
1260 \override #'(font-series . bold)
1264 \override #'(font-family . sans)
1272 @c FIXME: This needs an example -vv
1274 The size of the font may be set with the @code{font-size}
1275 property. The resulting size is taken relative to the
1276 @code{text-font-size} as defined in the @code{\paper} block.
1279 Although it is easy to switch between preconfigured fonts,
1280 it is also possible to use other fonts, as explained in the
1281 following sections: @ref{Single entry fonts} and
1282 @ref{Entire document fonts}.
1286 @ref{The Feta font},
1287 @ref{Music notation inside markup},
1288 @ref{Selecting font and font size},
1291 @node Single entry fonts
1292 @unnumberedsubsubsec Single entry fonts
1294 Any font that is installed on the operating system and recognized
1295 by FontConfig may be used in a score, using the following syntax:
1297 @lilypond[quote,verbatim,fragment,relative=1]
1298 \override Staff.TimeSignature #'font-name = #"Charter"
1299 \override Staff.TimeSignature #'font-size = #2
1303 \override #'(font-name . "Vera Bold")
1308 @funindex show-available-fonts
1310 The following command displays a list of all available fonts
1311 on the operating system:
1314 lilypond -dshow-available-fonts x
1318 The last argument of the command can be anything, but has to be
1323 @ref{Fonts explained},
1324 @ref{Entire document fonts}.
1330 @file{lily/@/font@/-config@/-scheme@/.cc}.
1332 @node Entire document fonts
1333 @unnumberedsubsubsec Entire document fonts
1336 It is possible to change the default font families for the
1337 entire document. In such a case, the following syntax has
1338 to be used, by providing three font families that will be
1339 respectively used as @emph{roman}, @emph{sans} and @emph{typewriter}
1340 fonts, as explained in @ref{Fonts explained}.
1342 @cindex font families, setting
1343 @funindex make-pango-font-tree
1345 @lilypond[verbatim,quote]
1349 (make-pango-font-tree "Times New Roman"
1352 (/ myStaffSize 20)))
1359 \typewriter typewriter. }
1363 @c we don't do Helvetica / Courier, since GS incorrectly loads
1368 @ref{Fonts explained},
1369 @ref{Single entry fonts},
1370 @ref{Selecting font and font size},