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
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,verbatim,relative=2]
64 a8^"pizz." g f e 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,verbatim,relative=2]
72 a8^\markup { \italic pizz. } g f e
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,verbatim,relative=2]
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,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,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,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[quote,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[quote,verbatim,relative=2]
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[quote,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,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 @c TODO Replace following example with this snippet when available
321 @c Submitted to LSR 30 Nov 08
322 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
323 {stand--alone-two--column-markup.ly}
326 Stand-alone text may be arranged in several columns using @code{\markup}
329 @lilypond[verbatim,quote]
334 \line {"O sacrum convivium" }
335 \line {"in quo Christus sumitur," }
336 \line {"recolitur memoria passionis ejus," }
337 \line {"mens impletur gratia," }
338 \line {"futurae gloriae nobis pignus datur." }
343 \line { \italic {"O sacred feast"} }
344 \line { \italic {"in which Christ is received,"} }
345 \line { \italic {"the memory of His Passion is renewed,"} }
346 \line { \italic {"the mind is filled with grace," } }
347 \line { \italic {"and a pledge of future glory is given to us." }}
348 \line { \italic {"Amen."}}
357 Notation Reference: @ref{Formatting text},
358 @ref{File structure},
359 @ref{Multiple scores in a book},
360 @ref{Multi-page markup}.
365 Internals Reference: @rinternals{TextScript}.
368 @node Formatting text
369 @subsection Formatting text
371 This section presents basic and advanced text formatting,
372 using the @code{\markup} mode specific syntax.
375 * Text markup introduction::
376 * Selecting font and font size::
378 * Graphic notation inside markup::
379 * Music notation inside markup::
380 * Multi-page markup::
383 @node Text markup introduction
384 @unnumberedsubsubsec Text markup introduction
392 A @code{\markup} block is used to typeset text with an extensible
393 syntax called @qq{markup mode}.
395 @cindex markup expressions
396 @cindex markup syntax
398 The markup syntax is similar to LilyPond's usual syntax: a
399 @code{\markup} expression is enclosed in curly braces @code{@{
400 @dots{} @}}. A single word is regarded as a minimal expression,
401 and therefore does not need to be enclosed with braces.
403 Unlike simple @qq{quoted text} indications, @code{\markup} blocks
404 may contain nested expressions or markup commands,
405 entered using the backslash @code{\} character.
406 Such commands only affect the first following expression.
408 @lilypond[quote,verbatim,relative=2]
410 a2^\markup { poco \italic più forte }
412 d2_\markup { \italic "string. assai" }
414 b1^\markup { \bold { molto \italic agitato } }
418 @cindex special characters in markup mode
419 @cindex markup mode, special characters
420 @cindex reserved characters, printing
421 @cindex printing special characters
422 @cindex quoted text in markup mode
424 A @code{\markup} block may also contain quoted text strings.
425 Such strings are treated as minimal text expressions, and
426 therefore any markup command or special character (such as
427 @code{\} and @code{#}) will be printed verbatim without affecting
428 the formatting of the text. Double quotation marks themselves
429 may be printed by preceding them with backslashes.
431 @lilypond[quote,verbatim,relative=2]
432 a1^"\italic markup..."
433 a_\markup { \italic "... prints \"italic\" letters!" }
437 To be treated as a distinct expression, a list of words needs
438 to be enclosed with double quotes or preceded by a command.
439 The way markup expressions are defined affects how these
440 expressions will be stacked, centered and aligned; in the
441 following example, the second @code{\markup} expression is
442 treated the same as the first one:
444 @lilypond[quote,verbatim,relative=2]
445 c1^\markup { \center-column { a bbb c } }
446 c1^\markup { \center-column { a { bbb c } } }
447 c1^\markup { \center-column { a \line { bbb c } } }
448 c1^\markup { \center-column { a "bbb c" } }
451 Markups can be stored in variables. Such variables may be
452 directly attached to notes:
454 @lilypond[quote,verbatim]
455 allegro = \markup { \bold \large Allegro }
465 An exhaustive list of @code{\markup}-specific commands can be found in
466 @ref{Text markup commands}.
471 @ref{Text markup commands}.
477 @file{scm/@/markup@/.scm}.
482 Syntax errors for markup mode can be confusing.
485 @node Selecting font and font size
486 @unnumberedsubsubsec Selecting font and font size
488 @cindex font switching
493 Basic font switching is supported in markup mode:
495 @lilypond[quote,verbatim,relative=2]
498 \italic { non troppo \underline Vivo }
501 d,_\markup { \italic quasi \smallCaps Tromba }
512 The size of the characters can also be altered in different ways:
515 the font size can be set to predefined standard sizes,
518 the font size can be set to an absolute value,
521 the font size can also be changed relatively to its previous value.
525 The following example demonstrates these three methods:
527 @lilypond[quote,verbatim,relative=1]
534 \fontsize #5 Sinfonia
541 \magnify #0.6 { e sentimento } )
551 Text may be printed as subscript or superscript. By default
552 these are printed in a smaller size, but a normal size can be used as well:
554 @lilypond[quote,verbatim]
557 \line { 1 \super st movement }
558 \line { 1 \normal-size-super st movement
559 \sub { (part two) } }
564 @cindex font families
566 The markup mode provides an easy way to select alternate
567 font families. The default serif font, of roman type, is
568 automatically selected unless specified otherwise; on the
569 last line of the following example, there is no difference
570 between the first and the second word.
572 @lilypond[quote,verbatim]
575 \line { Act \number 1 }
576 \line { \sans { Scene I. } }
577 \line { \typewriter { Verona. An open place. } }
578 \line { Enter \roman Valentine and Proteus. }
584 Some of these font families, used for specific items
585 such as numbers or dynamics, do not provide all
586 characters, as mentioned in @ref{New dynamic marks} and
587 @ref{Manual repeat marks}.
589 @c \concat is actually documented in Align (it is not
590 @c a font-switching command). But we need it here. -vv
592 When used inside a word, some font-switching or formatting
593 commands may produce an unwanted blank space. This can
594 easily be solved by concatenating the text elements together:
596 @lilypond[quote,verbatim]
600 \concat { 1 \super st }
604 \concat { \dynamic p , }
605 \italic { con dolce espressione }
611 An exhaustive list of font switching, and custom font usage
612 commands can be found in @ref{Font}.
614 Defining custom font sets is also possible, as explained in
625 @funindex \normalsize
641 @ref{New dynamic marks},
642 @ref{Manual repeat marks},
649 @rinternals{TextScript}.
652 @file{scm/@/define@/-markup@/-commands@/.scm}.
656 @unnumberedsubsubsec Text alignment
658 @cindex text, aligning
659 @cindex aligning text
661 This subsection discusses how to place text in markup mode.
662 Markup objects can also be moved as a whole, using the syntax
663 described in @rlearning{Moving objects}.
665 @c Padding commands should be mentioned on this page, but
666 @c most of these require \box to be more clearly illustrated. -vv
668 @cindex text, horizontal alignment
669 @cindex horizontal text alignment
670 @funindex \left-align
671 @funindex \center-align
672 @funindex \right-align
674 Markup objects may be aligned in different ways. By default,
675 a text indication is aligned on its left edge: in the following
676 example, there is no difference
677 between the first and the second markup.
679 @lilypond[quote,verbatim,relative=2]
682 d-\markup { \left-align poco }
684 d-\markup { \center-align { poco } }
686 d-\markup { \right-align poco }
691 Horizontal alignment may be fine-tuned
692 using a numeric value:
694 @lilypond[quote,verbatim,relative=2]
695 a1-\markup { \halign #-1 poco }
697 a,-\markup { \halign #0 poco }
699 a,-\markup { \halign #0.5 poco }
701 a,-\markup { \halign #2 poco }
705 Some objects may have alignment procedures of their own,
706 and therefore are not affected by these commands. It is
707 possible to move such markup objects as a whole, as shown
708 for instance in @ref{Text marks}.
710 @cindex text, vertical alignment
711 @cindex vertical text alignment
715 Vertical alignment is a bit more complex. As stated above,
716 markup objects can be moved as a whole; however, it is also
717 possible to move specific elements inside a markup block.
718 In this case, the element to be moved needs to be preceded
719 with an @emph{anchor point}, that can be another markup element
720 or an invisible object. The following example demonstrates these
721 two possibilities; the last markup in this example has no anchor
722 point, and therefore is not moved.
724 @lilypond[quote,verbatim,relative=1]
727 \raise #2 { Scène 1 }
732 \lower #4 \bold { Très modéré }
736 \raise #4 \italic { Une forêt. }
741 @funindex \general-align
743 @funindex \translate-scaled
745 Some commands can affect both the horizontal and vertical
746 alignment of text objects in markup mode. Any object
747 affected by these commands must be preceded with an
750 @lilypond[quote,verbatim,relative=1]
753 \translate #'(-1 . 2) "Scène 1"
758 \general-align #Y #3.2 \bold "Très modéré"
763 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
769 @funindex \center-column
771 @cindex multi-line markup
772 @cindex multi-line text
773 @cindex columns, text
775 A markup object may include several lines of text.
776 In the following example, each element or expression
777 is placed on its own line, either left-aligned or centered:
779 @lilypond[quote,verbatim]
797 @cindex centering text on the page
799 Similarly, a list of elements or expressions may be
800 spread to fill the entire horizontal line width (if there
801 is only one element, it will be centered on the page).
802 These expressions can, in turn, include multi-line text
803 or any other markup expression:
805 @lilypond[quote,verbatim]
808 \line { William S. Gilbert }
810 \huge \smallCaps "The Mikado"
812 \smallCaps "The Town of Titipu"
814 \line { Sir Arthur Sullivan }
825 @cindex wordwrapped text
826 @cindex justified text
828 Long text indications can also be automatically wrapped
829 accordingly to the given line width. These will be
830 either left-aligned or justified, as shown in
831 the following example.
833 @lilypond[quote,verbatim]
836 \line \smallCaps { La vida breve }
837 \line \bold { Acto I }
839 (La escena representa el corral de una casa de
840 gitanos en el AlbaicÃn de Granada. Al fondo una
841 puerta por la que se ve el negro interior de
842 una Fragua, iluminado por los rojos resplandores
847 \line \bold { Acto II }
848 \override #'(line-width . 50)
850 (Calle de Granada. Fachada de la casa de Carmela
851 y su hermano Manuel con grandes ventanas abiertas
852 a través de las que se ve el patio
853 donde se celebra una alegre fiesta)
859 An exhaustive list of text alignment commands
860 can be found in @ref{Align}.
865 @rlearning{Moving objects}.
874 Internals Reference: @rinternals{TextScript}.
877 @file{scm/@/define@/-markup@/-commands@/.scm}.
880 @node Graphic notation inside markup
881 @unnumberedsubsubsec Graphic notation inside markup
883 @cindex graphics, embedding
884 @cindex drawing graphic objects
886 Various graphic objects may be added to a score,
887 using markup commands.
891 @funindex \rounded-box
895 @cindex decorating text
898 Some markup commands allow decoration of text elements
899 with graphics, as demonstrated in the following example.
901 @lilypond[quote,verbatim]
910 \bracket "1866 - 1925"
913 \rounded-box \bold Prelude
918 @funindex \pad-markup
920 @funindex \pad-to-box
921 @funindex \pad-around
923 @cindex padding around text
926 Some commands may require an increase in the padding around
927 the text; this is achieved with some markup commands
928 exhaustively described in @ref{Align}.
930 @lilypond[quote,verbatim]
933 \box "Charles Ives (1874 - 1954)"
935 \box \pad-markup #2 "THE UNANSWERED QUESTION"
936 \box \pad-x #8 "A Cosmic Landscape"
943 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
944 \bold "Largo to Presto"
947 "String quartet keeps very even time,
948 Flute quartet keeps very uneven time."
953 @funindex \draw-circle
954 @funindex \filled-box
957 @funindex \arrow-head
959 @cindex graphic notation
960 @cindex symbols, non-musical
962 Other graphic elements or symbols may be printed
963 without requiring any text. As with any markup
964 expression, such objects can be combined.
966 @lilypond[quote,verbatim]
969 \draw-circle #4 #0.4 ##f
970 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
977 \arrow-head #Y #DOWN ##f
983 @funindex \postscript
985 @cindex embedded graphics
986 @cindex images, embedding
987 @cindex graphics, embedding
990 Advanced graphic features include the ability to
991 include external image files converted to the
992 Encapsulated PostScript format (@emph{eps}), or
993 to directly embed graphics into the input file,
994 using native PostScript code. In such a case, it
995 may be useful to explicitely specify the size of the
996 drawing, as demonstrated below:
998 @lilypond[quote,verbatim,relative=1]
1001 \epsfile #X #10 #"./context-example.eps"
1002 \with-dimensions #'(0 . 6) #'(0 . 10)
1018 An exhaustive list of graphics-specific commands
1019 can be found in @ref{Graphic}.
1025 @ref{Editorial annotations}.
1030 Internals Reference: @rinternals{TextScript}.
1033 @file{scm/@/define@/-markup@/-commands@/.scm},
1034 @file{scm/@/stencil@/.scm}.
1037 @node Music notation inside markup
1038 @unnumberedsubsubsec Music notation inside markup
1040 Various musical notation elements may be added
1041 to a score, inside a markup object.
1043 Notes and accidentals can be entered using markup
1046 @lilypond[quote,verbatim,relative=2]
1050 \note-by-number #1 #1 #1.5
1053 \natural \semiflat \flat
1054 \sesquiflat \doubleflat
1058 \natural \semisharp \sharp
1059 \sesquisharp \doublesharp
1064 Other notation objects may also be printed
1067 @lilypond[quote,verbatim,relative=1]
1074 fis_\markup { \dynamic rf }
1085 More generally, any available musical symbol may be
1086 included separately in a markup object, as demonstrated
1087 below; an exhaustive list of these symbols and their
1088 names can be found in @ref{The Feta font}.
1090 @lilypond[quote,verbatim,relative=2]
1092 c'^\markup { \musicglyph #"eight" }
1094 c,8._\markup { \musicglyph #"clefs.G_change" }
1096 c2^\markup { \musicglyph #"timesig.neomensural94" }
1099 @c TODO: add \lookup here? -vv
1100 @c Probably better not to document \lookup, which is useful only for
1101 @c printing braces, and instead document \left-brace and \right-brace
1102 @c when these become available -td
1105 Another way of printing non-text glyphs is described
1106 in @ref{Fonts explained}.
1108 The markup mode also supports diagrams for specific
1111 @lilypond[quote,verbatim,relative=2]
1113 \fret-diagram-terse #"x;x;o;2;3;2;"
1116 \harp-pedal #"^-v|--ov^"
1121 \musicglyph #"accordion.accDiscant"
1123 \raise #0.5 \musicglyph #"accordion.accDot"
1124 \raise #1.5 \musicglyph #"accordion.accDot"
1128 @c The accordion diagram is actually taken from a snippet.
1131 Such diagrams are documented in @ref{Instrument Specific Markup}.
1133 A whole score can even be nested inside a markup object.
1134 In such a case, the nested @code{\score} block must
1135 contain a @code{\layout} block, as demonstrated here:
1137 @lilypond[quote,verbatim,relative=1]
1140 \relative c' { c4 d e f }
1148 An exhaustive list of music notation related commands can be
1149 found in @ref{Music}.
1155 @ref{The Feta font},
1156 @ref{Fonts explained}.
1161 Internals Reference: @rinternals{TextScript}.
1164 @file{scm/@/define@/-markup@/-commands@/.scm},
1165 @file{scm/@/fret@/-diagrams@/.scm},
1166 @file{scm/@/harp@/-pedals@/.scm}.
1169 @node Multi-page markup
1170 @unnumberedsubsubsec Multi-page markup
1172 Although standard markup objects are not breakable, a
1173 specific syntax makes it possible to enter lines of text that can
1174 spread over multiple pages:
1176 @lilypond[quote,verbatim]
1179 A very long text of justified lines.
1183 Another very long paragraph.
1190 This syntax accepts a list of markups, that can be
1193 the result of a markup list command,
1197 a list of markup lists.
1200 An exhaustive list of markup list commands can be found in
1201 @ref{Text markup list commands}.
1206 @ref{Text markup list commands},
1207 @ref{New markup list command definition}.
1212 Internals Reference: @rinternals{TextScript}.
1215 @file{scm/@/define@/-markup@/-commands@/.scm}.
1219 @funindex \markuplines
1220 @code{\markuplines}.
1227 This section presents the way fonts are handled,
1228 and how they may be changed in scores.
1232 * Single entry fonts::
1233 * Entire document fonts::
1236 @node Fonts explained
1237 @unnumberedsubsubsec Fonts explained
1240 @cindex fonts, explained
1241 @funindex font-interface
1243 Fonts are handled through several libraries.
1244 FontConfig is used to detect available fonts on the system;
1245 the selected fonts are rendered using Pango.
1247 Music notation fonts can be described as a set of
1248 specific glyphs, ordered in several families.
1249 The following syntax allows various LilyPond @code{feta} non-text
1250 fonts to be used directly in markup mode:
1252 @lilypond[quote,verbatim,relative=2]
1255 \override #'(font-encoding . fetaBraces)
1257 \override #'(font-encoding . fetaNumber)
1259 \override #'(font-encoding . fetaDynamic)
1261 \override #'(font-encoding . fetaMusic)
1262 \lookup #"noteheads.s0petrucci"
1268 A simpler, but more limited syntax is also described in
1269 @ref{Music notation inside markup}.
1271 Three families of text fonts are made available: the
1272 @emph{roman} (serif) font, that defaults to New Century
1273 Schoolbook, the @emph{sans} font and the monospaced
1274 @emph{typewriter} font -- these last two families are
1275 determined by the Pango installation.
1277 Each family may include different shapes and series.
1278 The following example demonstrates the ability to select
1279 alternate families, shapes, series and sizes. The value
1280 supplied to @code{font-size} is the required change from the
1283 @lilypond[quote,verbatim,relative=2]
1284 \override Score.RehearsalMark #'font-family = #'typewriter
1285 \mark \markup "Ouverture"
1286 \override Voice.TextScript #'font-shape = #'italic
1287 \override Voice.TextScript #'font-series = #'bold
1288 d2.^\markup "Allegro"
1289 \override Voice.TextScript #'font-size = #-3
1294 A similar syntax may be used in markup mode, however in this case
1295 it is preferable to use the simpler syntax explained in
1296 @ref{Selecting font and font size}:
1298 @lilypond[quote,verbatim]
1302 \override #'(font-shape . italic)
1303 \override #'(font-size . 4)
1307 \override #'(font-family . typewriter)
1309 \override #'(font-series . bold)
1313 \override #'(font-family . sans)
1320 Although it is easy to switch between preconfigured fonts,
1321 it is also possible to use other fonts, as explained in the
1322 following sections: @ref{Single entry fonts} and
1323 @ref{Entire document fonts}.
1328 @ref{The Feta font},
1329 @ref{Music notation inside markup},
1330 @ref{Selecting font and font size},
1334 @node Single entry fonts
1335 @unnumberedsubsubsec Single entry fonts
1337 Any font that is installed on the operating system and recognized
1338 by FontConfig may be used in a score, using the following syntax:
1340 @lilypond[quote,verbatim,relative=2]
1341 \override Staff.TimeSignature #'font-name = #"Charter"
1342 \override Staff.TimeSignature #'font-size = #2
1346 \override #'(font-name . "Vera Bold")
1351 @funindex show-available-fonts
1353 The following command displays a list of all available fonts
1354 on the operating system:
1357 lilypond -dshow-available-fonts x
1361 The last argument of the command can be anything, but has to be
1367 @ref{Fonts explained},
1368 @ref{Entire document fonts}.
1374 @file{lily/@/font@/-config@/-scheme@/.cc}.
1377 @node Entire document fonts
1378 @unnumberedsubsubsec Entire document fonts
1380 It is possible to change the fonts to be used as the default fonts in
1381 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1382 specifying them, in that order, as shown in the example below. For an
1383 explanation of fonts, see @ref{Fonts explained}.
1385 @cindex font families, setting
1386 @funindex make-pango-font-tree
1388 @lilypond[verbatim,quote]
1392 (make-pango-font-tree "Times New Roman"
1395 (/ myStaffSize 20)))
1402 \typewriter typewriter. }
1406 @c we don't do Helvetica / Courier, since GS incorrectly loads
1412 @ref{Fonts explained},
1413 @ref{Single entry fonts},
1414 @ref{Selecting font and font size},