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
92 @code{\textLengthOff}.
98 @ref{Formatting text},
99 @ref{Direction and placement}.
105 @rinternals{TextScript}.
110 Checking to make sure that text scripts and lyrics are within the
111 margins is a relatively large computational task. To speed up
112 processing, LilyPond does not perform such calculations by
113 default; to enable it, use
116 \override Score.PaperColumn #'keep-inside-line = ##t
121 @unnumberedsubsubsec Text spanners
123 @cindex Text spanners
125 Some performance indications, e.g., @notation{rallentando} or
126 @notation{accelerando}, are written as text and are extended over
127 multiple notes with dotted lines.
128 Such objects, called @qq{spanners}, may be created
129 from one note to another using the following syntax:
131 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
132 \override TextSpanner #'(bound-details left text) = "rit."
138 The string to be printed is set through
139 object properties. By default it is printed in italic characters,
140 but different formatting can be obtained using
141 @code{\markup} blocks, as described in @ref{Formatting text}.
143 @lilypond[quote,ragged-right,fragment,relative=2,verbatim]
144 \override TextSpanner #'(bound-details left text) =
145 \markup { \upright "rit." }
150 The line style, as well as the text string, can be defined as an
151 object property. This syntax is described in @ref{Line styles}.
155 @funindex textSpannerUp
156 @code{\textSpannerUp},
157 @funindex textSpannerDown
158 @code{\textSpannerDown},
159 @funindex textSpannerNeutral
160 @code{\textSpannerNeutral}.
173 @rinternals{TextSpanner}.
177 @unnumberedsubsubsec Text marks
179 @cindex coda on bar line
180 @cindex segno on bar line
181 @cindex fermata on bar line
182 @cindex bar lines, symbols on
185 Various text elements may be added to a score using
186 the syntax described in @ref{Rehearsal marks}:
188 @c \mark needs to be placed on a separate line (it's not
189 @c attached to an object like \markup is). -vv
191 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
197 This syntax makes it possible to put any text on a bar line;
198 more complex text formatting may be added using a @code{\markup}
199 block, as described in @ref{Formatting text}:
201 @lilypond[fragment,quote,ragged-right,verbatim,relative=1]
203 \mark \markup { \italic { colla parte } }
209 This syntax also allows to print special signs, like coda, segno
210 or fermata, by specifying the appropriate symbol name as explained in
211 @ref{Music notation inside markup}:
213 @lilypond[fragment,quote,ragged-right,verbatim,relative=1]
215 \mark \markup { \musicglyph #"scripts.ufermata" }
220 Such objects are only typeset above the top staff of the score; depending on
221 whether they are specified at the end or the middle of a bar, they
222 can be placed above the bar line or between notes. When specified at a
223 line break, the mark will be printed at the beginning of the next line.
225 @lilypond[fragment,quote,ragged-right,verbatim,relative=2]
235 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
236 {printing-marks-at-the-end-of-a-line-or-a-score.ly}
238 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
239 {aligning-marks-with-various-notation-objects.ly}
241 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
242 {printing-marks-on-every-staff.ly}
247 @ref{Rehearsal marks},
248 @ref{Formatting text},
249 @ref{Music notation inside markup},
256 @rinternals{RehearsalMark}.
260 @c To be removed when Issue 69 in the tracker gets fixed. -vv
262 If a mark is entered at the end of the last bar of the score (where
263 there is no next line), then the mark will not be printed at
267 @unnumberedsubsubsec Separate text
269 @cindex separate text
270 @cindex standalone text
271 @cindex top-level text
272 @cindex text, standalone
275 A @code{\markup} block can exist by itself, outside of any
276 any @code{\score} block, as a @qq{top-level
277 expression}. This syntax is described in @ref{File structure}.
279 @lilypond[verbatim,quote]
281 Tomorrow, and tomorrow, and tomorrow...
286 This allows printing text separately
287 from the music, which is particularly
288 useful when the input file contains
289 several music pieces, as described in
290 @ref{Multiple scores in a book}.
292 @lilypond[quote,ragged-right,verbatim]
297 Tomorrow, and tomorrow, and tomorrow...
304 Separate text blocks can be spread over multiple pages,
305 making it possible to print text documents or books entirely
306 within LilyPond. This feature, and the specific syntax it
307 requires, are described in @ref{Multi-page markup}.
311 @funindex \markuplines
320 TODO: add convenient snippets in input/new -vv
325 Notation Reference: @ref{Formatting text},
326 @ref{File structure},
327 @ref{Multiple scores in a book},
328 @ref{Multi-page markup}.
333 Internals Reference: @rinternals{TextScript}.
336 @node Formatting text
337 @subsection Formatting text
339 This section presents basic and advanced text formatting,
340 using the @code{\markup} mode specific syntax.
343 * Text markup introduction::
344 * Selecting font and font size::
346 * Graphic notation inside markup::
347 * Music notation inside markup::
348 * Multi-page markup::
351 @node Text markup introduction
352 @unnumberedsubsubsec Text markup introduction
360 A @code{\markup} block is used to typeset text with an extensible
361 syntax called @qq{markup mode}.
363 @cindex markup expressions
364 @cindex markup syntax
366 The markup syntax is similar to LilyPond's usual syntax: a
367 @code{\markup} expression is enclosed in curly braces @code{@{
368 @dots{} @}}. A single word is regarded as a minimal expression,
369 and therefore does not need to be enclosed with braces.
371 Unlike simple @qq{quoted text} indications, @code{\markup} blocks
372 may contain nested expressions or markup commands,
373 entered using the backslash @code{\} character.
374 Such commands only affect the first following expression.
376 @lilypond[quote,verbatim,fragment,relative=1]
378 a2^\markup { poco \italic più forte }
380 d2_\markup { \italic "string. assai" }
382 b1^\markup { \bold { molto \italic agitato } }
386 @cindex special characters in markup mode
387 @cindex markup mode, special characters
388 @cindex reserved characters, printing
389 @cindex printing special characters
390 @cindex quoted text in markup mode
392 A @code{\markup} block may also contain quoted text strings.
393 Such strings are treated as minimal text expressions, and
394 therefore any markup command or special character (such as
395 @code{\} and @code{#}) will be printed verbatim without affecting
396 the formatting of the text. Double quotation marks themselves
397 may be printed by preceding them with backslashes.
399 @lilypond[quote,verbatim,fragment,relative=1]
400 d1^"\italic markup..."
401 d_\markup { \italic "... prints \"italic\" letters!" }
405 To be treated as a distinct expression, a list of words needs
406 to be enclosed with double quotes or preceded by a command.
407 The way markup expressions are defined affects how these
408 expressions will be stacked, centered and aligned; in the
409 following example, the second @code{\markup} expression is
410 treated the same as the first one:
412 @lilypond[quote,verbatim,fragment,relative=1]
413 c1^\markup { \center-column { a bbb c } }
414 c1^\markup { \center-column { a { bbb c } } }
415 c1^\markup { \center-column { a \line { bbb c } } }
416 c1^\markup { \center-column { a "bbb c" } }
419 Markups can be stored in variables. Such variables may be
420 directly attached to notes:
422 @lilypond[quote,verbatim]
423 allegro = \markup { \bold \large Allegro }
433 An exhaustive list of @code{\markup}-specific commands can be found in
434 @ref{Text markup commands}.
439 @ref{Text markup commands}.
445 @file{scm/@/markup@/.scm}.
450 Syntax errors for markup mode can be confusing.
453 @node Selecting font and font size
454 @unnumberedsubsubsec Selecting font and font size
456 @cindex font switching
461 Basic font switching is supported in markup mode:
463 @lilypond[quote,verbatim,relative=2]
466 \italic { non troppo \underline Vivo }
469 d,_\markup { \italic quasi \smallCaps Tromba }
480 The size of the characters can also be altered in different ways:
483 the font size can be set to predefined standard sizes,
486 the font size can be set to an absolute value,
489 the font size can also be changed relatively to its previous value.
493 The following example demonstrates these three methods:
495 @lilypond[quote,verbatim,relative=1]
502 \fontsize #5 Sinfonia
509 \magnify #0.6 { e sentimento } )
519 Text may be printed as subscript or superscript. By default
520 these are printed in a smaller size, but a normal size can be used as well:
522 @lilypond[quote,verbatim]
525 \line { 1 \super st movement }
526 \line { 1 \normal-size-super st movement
527 \sub { (part two) } }
532 @cindex font families
534 The markup mode provides an easy way to select alternate
535 font families. The default serif font, of roman type, is
536 automatically selected unless specified otherwise; on the
537 last line of the following example, there is no difference
538 between the first and the second word.
540 @lilypond[quote,verbatim]
543 \line { Act \number 1 }
544 \line { \sans { Scene I. } }
545 \line { \typewriter { Verona. An open place. } }
546 \line { Enter \roman Valentine and Proteus. }
552 Some of these font families, used for specific items
553 such as numbers or dynamics, do not provide all
554 characters, as mentioned in @ref{New dynamic marks} and
555 @ref{Manual repeat marks}.
557 @c \concat is actually documented in Align (it is not
558 @c a font-switching command). But we need it here. -vv
560 When used inside a word, some font-switching or formatting
561 commands may produce an unwanted blank space. This can
562 easily be solved by concatenating the text elements together:
564 @lilypond[quote,verbatim]
568 \concat { 1 \super st }
572 \concat { \dynamic p , }
573 \italic { con dolce espressione }
579 An exhaustive list of font switching, and custom font usage
580 commands can be found in @ref{Font}.
582 Defining custom font sets is also possible, as explained in
593 @funindex \normalsize
609 @ref{New dynamic marks},
610 @ref{Manual repeat marks},
617 @rinternals{TextScript}.
620 @file{scm/@/define@/-markup@/-commands@/.scm}.
624 @unnumberedsubsubsec Text alignment
626 @cindex text, aligning
627 @cindex aligning text
629 This subsection discusses how to place text in markup mode.
630 Markup objects can also be moved as a whole, using the syntax
631 described in @rlearning{Moving objects}.
633 @c Padding commands should be mentioned on this page, but
634 @c most of these require \box to be more clearly illustrated. -vv
636 @cindex text, horizontal alignment
637 @cindex horizontal text alignment
638 @funindex \left-align
639 @funindex \center-align
640 @funindex \right-align
642 Markup objects may be aligned in different ways. By default,
643 a text indication is aligned on its left edge: in the following
644 example, there is no difference
645 between the first and the second markup.
647 @lilypond[quote,verbatim,fragment,relative=1]
650 d-\markup { \left-align poco }
652 d-\markup { \center-align { poco } }
654 d-\markup { \right-align poco }
659 Horizontal alignment may be fine-tuned
660 using a numeric value:
662 @lilypond[quote,verbatim,fragment,relative=1]
663 a1-\markup { \halign #-1 poco }
665 a,-\markup { \halign #0 poco }
667 a,-\markup { \halign #0.5 poco }
669 a,-\markup { \halign #2 poco }
673 Some objects may have alignment procedures of their own,
674 and therefore are not affected by these commands. It is
675 possible to move such markup objects as a whole, as shown
676 for instance in @ref{Text marks}.
678 @cindex text, vertical alignment
679 @cindex vertical text alignment
683 Vertical alignment is a bit more complex. As stated above,
684 markup objects can be moved as a whole; however, it is also
685 possible to move specific elements inside a markup block.
686 In this case, the element to be moved needs to be preceded
687 with an @emph{anchor point}, that can be another markup element
688 or an invisible object. The following example demonstrates these
689 two possibilities; the last markup in this example has no anchor
690 point, and therefore is not moved.
692 @lilypond[quote,verbatim,fragment,relative=1]
695 \raise #2 { Scène 1 }
700 \lower #4 \bold { Très modéré }
704 \raise #4 \italic { Une forêt. }
709 @funindex \general-align
711 @funindex \translate-scaled
713 Some commands can affect both the horizontal and vertical
714 alignment of text objects in markup mode. Any object
715 affected by these commands must be preceded with an
718 @lilypond[quote,verbatim,fragment,relative=1]
721 \translate #'(-1 . 2) "Scène 1"
726 \general-align #Y #3.2 \bold "Très modéré"
731 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
737 @funindex \center-column
739 @cindex multi-line markup
740 @cindex multi-line text
741 @cindex columns, text
743 A markup object may include several lines of text.
744 In the following example, each element or expression
745 is placed on its own line, either left-aligned or centered:
747 @lilypond[quote,verbatim]
765 @cindex centering text on the page
767 Similarly, a list of elements or expressions may be
768 spread to fill the entire horizontal line width (if there
769 is only one element, it will be centered on the page).
770 These expressions can, in turn, include multi-line text
771 or any other markup expression:
773 @lilypond[quote,verbatim]
776 \line { William S. Gilbert }
778 \huge \smallCaps "The Mikado"
780 \smallCaps "The Town of Titipu"
782 \line { Sir Arthur Sullivan }
793 @cindex wordwrapped text
794 @cindex justified text
796 Long text indications can also be automatically wrapped
797 accordingly to the given line width. These will be
798 either left-aligned or justified, as shown in
799 the following example.
801 @lilypond[quote,verbatim]
804 \line \smallCaps { La vida breve }
805 \line \bold { Acto I }
807 (La escena representa el corral de una casa de
808 gitanos en el AlbaicÃn de Granada. Al fondo una
809 puerta por la que se ve el negro interior de
810 una Fragua, iluminado por los rojos resplandores
815 \line \bold { Acto II }
816 \override #'(line-width . 50)
818 (Calle de Granada. Fachada de la casa de Carmela
819 y su hermano Manuel con grandes ventanas abiertas
820 a través de las que se ve el patio
821 donde se celebra una alegre fiesta)
827 An exhaustive list of text alignment commands
828 can be found in @ref{Align}.
833 @rlearning{Moving objects}.
842 Internals Reference: @rinternals{TextScript}.
845 @file{scm/@/define@/-markup@/-commands@/.scm}.
848 @node Graphic notation inside markup
849 @unnumberedsubsubsec Graphic notation inside markup
851 @cindex graphics, embedding
852 @cindex drawing graphic objects
854 Various graphic objects may be added to a score,
855 using markup commands.
859 @funindex \rounded-box
863 @cindex decorating text
866 Some markup commands allow decoration of text elements
867 with graphics, as demonstrated in the following example.
869 @lilypond[quote,verbatim]
878 \bracket "1866 - 1925"
881 \rounded-box \bold Prelude
886 @funindex \pad-markup
888 @funindex \pad-to-box
889 @funindex \pad-around
891 @cindex padding around text
894 Some commands may require an increase in the padding around
895 the text; this is achieved with some markup commands
896 exhaustively described in @ref{Align}.
898 @lilypond[quote,verbatim]
901 \box "Charles Ives (1874 - 1954)"
903 \box \pad-markup #2 "THE UNANSWERED QUESTION"
904 \box \pad-x #8 "A Cosmic Landscape"
911 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
912 \bold "Largo to Presto"
915 "String quartet keeps very even time,
916 Flute quartet keeps very uneven time."
921 @funindex \draw-circle
922 @funindex \filled-box
925 @funindex \arrow-head
927 @cindex graphic notation
928 @cindex symbols, non-musical
930 Other graphic elements or symbols may be printed
931 without requiring any text. As with any markup
932 expression, such objects can be combined.
934 @lilypond[quote,verbatim]
937 \draw-circle #4 #0.4 ##f
938 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
945 \arrow-head #Y #DOWN ##f
951 @funindex \postscript
953 @cindex embedded graphics
954 @cindex images, embedding
955 @cindex graphics, embedding
958 Advanced graphic features include the ability to
959 include external image files converted to the
960 Encapsulated PostScript format (@emph{eps}), or
961 to directly embed graphics into the input file,
962 using native PostScript code. In such a case, it
963 may be useful to explicitely specify the size of the
964 drawing, as demonstrated below:
966 @lilypond[quote,verbatim,fragment,relative=1]
969 \epsfile #X #10 #"./context-example.eps"
970 \with-dimensions #'(0 . 6) #'(0 . 10)
986 An exhaustive list of graphics-specific commands
987 can be found in @ref{Graphic}.
993 @ref{Editorial annotations}.
998 Internals Reference: @rinternals{TextScript}.
1001 @file{scm/@/define@/-markup@/-commands@/.scm},
1002 @file{scm/@/stencil@/.scm}.
1005 @node Music notation inside markup
1006 @unnumberedsubsubsec Music notation inside markup
1008 Various musical notation elements may be added
1009 to a score, inside a markup object.
1011 Notes and accidentals can be entered using markup
1014 @lilypond[quote,verbatim,fragment,relative=2]
1018 \note-by-number #1 #1 #1.5
1021 \natural \semiflat \flat
1022 \sesquiflat \doubleflat
1026 \natural \semisharp \sharp
1027 \sesquisharp \doublesharp
1032 Other notation objects may also be printed
1035 @lilypond[quote,verbatim,fragment,relative=1]
1042 fis_\markup { \dynamic rf }
1053 More generally, any available musical symbol may be
1054 included separately in a markup object, as demonstrated
1055 below; an exhaustive list of these symbols and their
1056 names can be found in @ref{The Feta font}.
1058 @lilypond[quote,verbatim,fragment,relative=2]
1060 c'^\markup { \musicglyph #"eight" }
1062 c,8._\markup { \musicglyph #"clefs.G_change" }
1064 c2^\markup { \musicglyph #"timesig.neomensural94" }
1066 @c TODO: add \lookup here? -vv
1069 Another way of printing non-text glyphs is described
1070 in @ref{Fonts explained}.
1072 The markup mode also supports diagrams for specific
1075 @lilypond[quote,verbatim,fragment,relative=2]
1077 \fret-diagram-terse #"x;x;o;2;3;2;"
1080 \harp-pedal #"^-v|--ov^"
1085 \musicglyph #"accordion.accDiscant"
1087 \raise #0.5 \musicglyph #"accordion.accDot"
1088 \raise #1.5 \musicglyph #"accordion.accDot"
1092 @c The accordion diagram is actually taken from a snippet.
1095 Such diagrams are documented in @ref{Instrument Specific Markup}.
1097 A whole score can even be nested inside a markup object.
1098 In such a case, the nested @code{\score} block must
1099 contain a @code{\layout} block, as demonstrated here:
1101 @lilypond[quote,verbatim,fragment,relative=1]
1104 \relative { c4 d e f }
1112 An exhaustive list of music notation related commands can be
1113 found in @ref{Music}.
1119 @ref{The Feta font},
1120 @ref{Fonts explained}.
1125 Internals Reference: @rinternals{TextScript}.
1128 @file{scm/@/define@/-markup@/-commands@/.scm},
1129 @file{scm/@/fret@/-diagrams@/.scm},
1130 @file{scm/@/harp@/-pedals@/.scm}.
1133 @node Multi-page markup
1134 @unnumberedsubsubsec Multi-page markup
1136 Although standard markup objects are not breakable, a
1137 specific syntax makes it possible to enter lines of text that can
1138 spread over multiple pages:
1140 @lilypond[quote,verbatim]
1143 A very long text of justified lines.
1147 Another very long paragraph.
1154 This syntax accepts a list of markups, that can be
1157 the result of a markup list command,
1161 a list of markup lists.
1164 An exhaustive list of markup list commands can be found in
1165 @ref{Text markup list commands}.
1170 @ref{Text markup list commands},
1171 @ref{New markup list command definition}.
1176 Internals Reference: @rinternals{TextScript}.
1179 @file{scm/@/define@/-markup@/-commands@/.scm}.
1183 @funindex \markuplines
1184 @code{\markuplines}.
1191 This section presents the way fonts are handled,
1192 and how they may be changed in scores.
1196 * Single entry fonts::
1197 * Entire document fonts::
1200 @node Fonts explained
1201 @unnumberedsubsubsec Fonts explained
1204 @cindex fonts, explained
1205 @funindex font-interface
1207 Fonts are handled through several libraries.
1208 FontConfig is used to detect available fonts on the system;
1209 the selected fonts are rendered using Pango.
1211 Music notation fonts can be described as a set of
1212 specific glyphs, ordered in several families.
1213 The following syntax allows various LilyPond @code{feta} non-text
1214 fonts to be used directly in markup mode:
1216 @lilypond[quote,verbatim,fragment,relative=2]
1219 \override #'(font-encoding . fetaBraces)
1221 \override #'(font-encoding . fetaNumber)
1223 \override #'(font-encoding . fetaDynamic)
1225 \override #'(font-encoding . fetaMusic)
1226 \lookup #"noteheads.s0petrucci"
1232 A simpler, but more limited syntax is also described in
1233 @ref{Music notation inside markup}.
1235 Three families of text fonts are made available: the
1236 @emph{roman} (serif) font, that defaults to New Century
1237 Schoolbook, the @emph{sans} font and the monospaced
1238 @emph{typewriter} font -- these last two families are
1239 determined by the Pango installation.
1241 Each family may include different shapes and series.
1242 The following example demonstrates the ability to select
1243 alternate families, shapes, series and sizes:
1245 @lilypond[quote,verbatim,fragment,relative=2]
1246 \override Score.RehearsalMark #'font-family = #'typewriter
1247 \mark \markup "Ouverture"
1249 \override Voice.TextScript #'font-shape = #'italic
1250 \override Voice.TextScript #'font-series = #'bold
1251 d'2.^\markup "Allegro"
1256 A similar syntax may be used in markup mode, however in this case
1257 it is preferable to use the simpler syntax explained in
1258 @ref{Selecting font and font size}:
1260 @lilypond[quote,verbatim]
1264 \override #'(font-shape . italic)
1265 \override #'(font-size . 4)
1269 \override #'(font-family . typewriter)
1271 \override #'(font-series . bold)
1275 \override #'(font-family . sans)
1283 @c FIXME: This needs an example -vv
1285 The size of the font may be set with the @code{font-size}
1286 property. The resulting size is taken relative to the
1287 @code{text-font-size} as defined in the @code{\paper} block.
1290 Although it is easy to switch between preconfigured fonts,
1291 it is also possible to use other fonts, as explained in the
1292 following sections: @ref{Single entry fonts} and
1293 @ref{Entire document fonts}.
1298 @ref{The Feta font},
1299 @ref{Music notation inside markup},
1300 @ref{Selecting font and font size},
1304 @node Single entry fonts
1305 @unnumberedsubsubsec Single entry fonts
1307 Any font that is installed on the operating system and recognized
1308 by FontConfig may be used in a score, using the following syntax:
1310 @lilypond[quote,verbatim,fragment,relative=1]
1311 \override Staff.TimeSignature #'font-name = #"Charter"
1312 \override Staff.TimeSignature #'font-size = #2
1316 \override #'(font-name . "Vera Bold")
1321 @funindex show-available-fonts
1323 The following command displays a list of all available fonts
1324 on the operating system:
1327 lilypond -dshow-available-fonts x
1331 The last argument of the command can be anything, but has to be
1337 @ref{Fonts explained},
1338 @ref{Entire document fonts}.
1344 @file{lily/@/font@/-config@/-scheme@/.cc}.
1347 @node Entire document fonts
1348 @unnumberedsubsubsec Entire document fonts
1350 It is possible to change the fonts to be used as the default fonts in
1351 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1352 specifying them, in that order, as shown in the example below. For an
1353 explanation of fonts, see @ref{Fonts explained}.
1355 @cindex font families, setting
1356 @funindex make-pango-font-tree
1358 @lilypond[verbatim,quote]
1362 (make-pango-font-tree "Times New Roman"
1365 (/ myStaffSize 20)))
1372 \typewriter typewriter. }
1376 @c we don't do Helvetica / Courier, since GS incorrectly loads
1382 @ref{Fonts explained},
1383 @ref{Single entry fonts},
1384 @ref{Selecting font and font size},