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
319 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
320 {stand-alone-two-column-markup.ly}
323 Notation Reference: @ref{Formatting text},
324 @ref{File structure},
325 @ref{Multiple scores in a book},
326 @ref{Multi-page markup}.
331 Internals Reference: @rinternals{TextScript}.
334 @node Formatting text
335 @subsection Formatting text
337 This section presents basic and advanced text formatting,
338 using the @code{\markup} mode specific syntax.
341 * Text markup introduction::
342 * Selecting font and font size::
344 * Graphic notation inside markup::
345 * Music notation inside markup::
346 * Multi-page markup::
349 @node Text markup introduction
350 @unnumberedsubsubsec Text markup introduction
358 A @code{\markup} block is used to typeset text with an extensible
359 syntax called @qq{markup mode}.
361 @cindex markup expressions
362 @cindex markup syntax
364 The markup syntax is similar to LilyPond's usual syntax: a
365 @code{\markup} expression is enclosed in curly braces @code{@{
366 @dots{} @}}. A single word is regarded as a minimal expression,
367 and therefore does not need to be enclosed with braces.
369 Unlike simple @qq{quoted text} indications, @code{\markup} blocks
370 may contain nested expressions or markup commands,
371 entered using the backslash @code{\} character.
372 Such commands only affect the first following expression.
374 @lilypond[quote,verbatim,relative=2]
376 a2^\markup { poco \italic più forte }
378 d2_\markup { \italic "string. assai" }
380 b1^\markup { \bold { molto \italic agitato } }
384 @cindex special characters in markup mode
385 @cindex markup mode, special characters
386 @cindex reserved characters, printing
387 @cindex printing special characters
388 @cindex quoted text in markup mode
390 A @code{\markup} block may also contain quoted text strings.
391 Such strings are treated as minimal text expressions, and
392 therefore any markup command or special character (such as
393 @code{\} and @code{#}) will be printed verbatim without affecting
394 the formatting of the text. Double quotation marks themselves
395 may be printed by preceding them with backslashes.
397 @lilypond[quote,verbatim,relative=2]
398 a1^"\italic markup..."
399 a_\markup { \italic "... prints \"italic\" letters!" }
403 To be treated as a distinct expression, a list of words needs
404 to be enclosed with double quotes or preceded by a command.
405 The way markup expressions are defined affects how these
406 expressions will be stacked, centered and aligned; in the
407 following example, the second @code{\markup} expression is
408 treated the same as the first one:
410 @lilypond[quote,verbatim,relative=2]
411 c1^\markup { \center-column { a bbb c } }
412 c1^\markup { \center-column { a { bbb c } } }
413 c1^\markup { \center-column { a \line { bbb c } } }
414 c1^\markup { \center-column { a "bbb c" } }
417 Markups can be stored in variables. Such variables may be
418 directly attached to notes:
420 @lilypond[quote,verbatim]
421 allegro = \markup { \bold \large Allegro }
431 An exhaustive list of @code{\markup}-specific commands can be found in
432 @ref{Text markup commands}.
437 @ref{Text markup commands}.
443 @file{scm/@/markup@/.scm}.
448 Syntax errors for markup mode can be confusing.
451 @node Selecting font and font size
452 @unnumberedsubsubsec Selecting font and font size
454 @cindex font switching
459 Basic font switching is supported in markup mode:
461 @lilypond[quote,verbatim,relative=2]
464 \italic { non troppo \underline Vivo }
467 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=1]
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, and custom font usage
578 commands can be found in @ref{Font}.
580 Defining custom font sets is also possible, as explained in
591 @funindex \normalsize
607 @ref{New dynamic marks},
608 @ref{Manual repeat marks},
615 @rinternals{TextScript}.
618 @file{scm/@/define@/-markup@/-commands@/.scm}.
622 @unnumberedsubsubsec Text alignment
624 @cindex text, aligning
625 @cindex aligning text
627 This subsection discusses how to place text in markup mode.
628 Markup objects can also be moved as a whole, using the syntax
629 described in @rlearning{Moving objects}.
631 @c Padding commands should be mentioned on this page, but
632 @c most of these require \box to be more clearly illustrated. -vv
634 @cindex text, horizontal alignment
635 @cindex horizontal text alignment
636 @funindex \left-align
637 @funindex \center-align
638 @funindex \right-align
640 Markup objects may be aligned in different ways. By default,
641 a text indication is aligned on its left edge: in the following
642 example, there is no difference
643 between the first and the second markup.
645 @lilypond[quote,verbatim,relative=2]
648 d-\markup { \left-align poco }
650 d-\markup { \center-align { poco } }
652 d-\markup { \right-align poco }
657 Horizontal alignment may be fine-tuned
658 using a numeric value:
660 @lilypond[quote,verbatim,relative=2]
661 a1-\markup { \halign #-1 poco }
663 a,-\markup { \halign #0 poco }
665 a,-\markup { \halign #0.5 poco }
667 a,-\markup { \halign #2 poco }
671 Some objects may have alignment procedures of their own,
672 and therefore are not affected by these commands. It is
673 possible to move such markup objects as a whole, as shown
674 for instance in @ref{Text marks}.
676 @cindex text, vertical alignment
677 @cindex vertical text alignment
681 Vertical alignment is a bit more complex. As stated above,
682 markup objects can be moved as a whole; however, it is also
683 possible to move specific elements inside a markup block.
684 In this case, the element to be moved needs to be preceded
685 with an @emph{anchor point}, that can be another markup element
686 or an invisible object. The following example demonstrates these
687 two possibilities; the last markup in this example has no anchor
688 point, and therefore is not moved.
690 @lilypond[quote,verbatim,relative=1]
693 \raise #2 { Scène 1 }
698 \lower #4 \bold { Très modéré }
702 \raise #4 \italic { Une forêt. }
707 @funindex \general-align
709 @funindex \translate-scaled
711 Some commands can affect both the horizontal and vertical
712 alignment of text objects in markup mode. Any object
713 affected by these commands must be preceded with an
716 @lilypond[quote,verbatim,relative=1]
719 \translate #'(-1 . 2) "Scène 1"
724 \general-align #Y #3.2 \bold "Très modéré"
729 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
735 @funindex \center-column
737 @cindex multi-line markup
738 @cindex multi-line text
739 @cindex columns, text
741 A markup object may include several lines of text.
742 In the following example, each element or expression
743 is placed on its own line, either left-aligned or centered:
745 @lilypond[quote,verbatim]
763 @cindex centering text on the page
765 Similarly, a list of elements or expressions may be
766 spread to fill the entire horizontal line width (if there
767 is only one element, it will be centered on the page).
768 These expressions can, in turn, include multi-line text
769 or any other markup expression:
771 @lilypond[quote,verbatim]
774 \line { William S. Gilbert }
776 \huge \smallCaps "The Mikado"
778 \smallCaps "The Town of Titipu"
780 \line { Sir Arthur Sullivan }
791 @cindex wordwrapped text
792 @cindex justified text
794 Long text indications can also be automatically wrapped
795 accordingly to the given line width. These will be
796 either left-aligned or justified, as shown in
797 the following example.
799 @lilypond[quote,verbatim]
802 \line \smallCaps { La vida breve }
803 \line \bold { Acto I }
805 (La escena representa el corral de una casa de
806 gitanos en el AlbaicÃn de Granada. Al fondo una
807 puerta por la que se ve el negro interior de
808 una Fragua, iluminado por los rojos resplandores
813 \line \bold { Acto II }
814 \override #'(line-width . 50)
816 (Calle de Granada. Fachada de la casa de Carmela
817 y su hermano Manuel con grandes ventanas abiertas
818 a través de las que se ve el patio
819 donde se celebra una alegre fiesta)
825 An exhaustive list of text alignment commands
826 can be found in @ref{Align}.
831 @rlearning{Moving objects}.
840 Internals Reference: @rinternals{TextScript}.
843 @file{scm/@/define@/-markup@/-commands@/.scm}.
846 @node Graphic notation inside markup
847 @unnumberedsubsubsec Graphic notation inside markup
849 @cindex graphics, embedding
850 @cindex drawing graphic objects
852 Various graphic objects may be added to a score,
853 using markup commands.
857 @funindex \rounded-box
861 @cindex decorating text
864 Some markup commands allow decoration of text elements
865 with graphics, as demonstrated in the following example.
867 @lilypond[quote,verbatim]
876 \bracket "1866 - 1925"
879 \rounded-box \bold Prelude
884 @funindex \pad-markup
886 @funindex \pad-to-box
887 @funindex \pad-around
889 @cindex padding around text
892 Some commands may require an increase in the padding around
893 the text; this is achieved with some markup commands
894 exhaustively described in @ref{Align}.
896 @lilypond[quote,verbatim]
899 \box "Charles Ives (1874 - 1954)"
901 \box \pad-markup #2 "THE UNANSWERED QUESTION"
902 \box \pad-x #8 "A Cosmic Landscape"
909 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
910 \bold "Largo to Presto"
913 "String quartet keeps very even time,
914 Flute quartet keeps very uneven time."
919 @funindex \draw-circle
920 @funindex \filled-box
923 @funindex \arrow-head
925 @cindex graphic notation
926 @cindex symbols, non-musical
928 Other graphic elements or symbols may be printed
929 without requiring any text. As with any markup
930 expression, such objects can be combined.
932 @lilypond[quote,verbatim]
935 \draw-circle #4 #0.4 ##f
936 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
943 \arrow-head #Y #DOWN ##f
949 @funindex \postscript
951 @cindex embedded graphics
952 @cindex images, embedding
953 @cindex graphics, embedding
956 Advanced graphic features include the ability to
957 include external image files converted to the
958 Encapsulated PostScript format (@emph{eps}), or
959 to directly embed graphics into the input file,
960 using native PostScript code. In such a case, it
961 may be useful to explicitely specify the size of the
962 drawing, as demonstrated below:
964 @lilypond[quote,verbatim,relative=1]
967 \epsfile #X #10 #"./context-example.eps"
968 \with-dimensions #'(0 . 6) #'(0 . 10)
984 An exhaustive list of graphics-specific commands
985 can be found in @ref{Graphic}.
991 @ref{Editorial annotations}.
996 Internals Reference: @rinternals{TextScript}.
999 @file{scm/@/define@/-markup@/-commands@/.scm},
1000 @file{scm/@/stencil@/.scm}.
1003 @node Music notation inside markup
1004 @unnumberedsubsubsec Music notation inside markup
1006 Various musical notation elements may be added
1007 to a score, inside a markup object.
1009 Notes and accidentals can be entered using markup
1012 @lilypond[quote,verbatim,relative=2]
1016 \note-by-number #1 #1 #1.5
1019 \natural \semiflat \flat
1020 \sesquiflat \doubleflat
1024 \natural \semisharp \sharp
1025 \sesquisharp \doublesharp
1030 Other notation objects may also be printed
1033 @lilypond[quote,verbatim,relative=1]
1040 fis_\markup { \dynamic rf }
1051 More generally, any available musical symbol may be
1052 included separately in a markup object, as demonstrated
1053 below; an exhaustive list of these symbols and their
1054 names can be found in @ref{The Feta font}.
1056 @lilypond[quote,verbatim,relative=2]
1058 c'^\markup { \musicglyph #"eight" }
1060 c,8._\markup { \musicglyph #"clefs.G_change" }
1062 c2^\markup { \musicglyph #"timesig.neomensural94" }
1065 @c TODO: add \lookup here? -vv
1066 @c Probably better not to document \lookup, which is useful only for
1067 @c printing braces, and instead document \left-brace and \right-brace
1068 @c when these become available -td
1071 Another way of printing non-text glyphs is described
1072 in @ref{Fonts explained}.
1074 The markup mode also supports diagrams for specific
1077 @lilypond[quote,verbatim,relative=2]
1079 \fret-diagram-terse #"x;x;o;2;3;2;"
1082 \harp-pedal #"^-v|--ov^"
1087 \musicglyph #"accordion.accDiscant"
1089 \raise #0.5 \musicglyph #"accordion.accDot"
1090 \raise #1.5 \musicglyph #"accordion.accDot"
1094 @c The accordion diagram is actually taken from a snippet.
1097 Such diagrams are documented in @ref{Instrument Specific Markup}.
1099 A whole score can even be nested inside a markup object.
1100 In such a case, the nested @code{\score} block must
1101 contain a @code{\layout} block, as demonstrated here:
1103 @lilypond[quote,verbatim,relative=1]
1106 \relative c' { c4 d e f }
1114 An exhaustive list of music notation related commands can be
1115 found in @ref{Music}.
1121 @ref{The Feta font},
1122 @ref{Fonts explained}.
1127 Internals Reference: @rinternals{TextScript}.
1130 @file{scm/@/define@/-markup@/-commands@/.scm},
1131 @file{scm/@/fret@/-diagrams@/.scm},
1132 @file{scm/@/harp@/-pedals@/.scm}.
1135 @node Multi-page markup
1136 @unnumberedsubsubsec Multi-page markup
1138 Although standard markup objects are not breakable, a
1139 specific syntax makes it possible to enter lines of text that can
1140 spread over multiple pages:
1142 @lilypond[quote,verbatim]
1145 A very long text of justified lines.
1149 Another very long paragraph.
1156 This syntax accepts a list of markups, that can be
1159 the result of a markup list command,
1163 a list of markup lists.
1166 An exhaustive list of markup list commands can be found in
1167 @ref{Text markup list commands}.
1172 @ref{Text markup list commands},
1173 @ref{New markup list command definition}.
1178 Internals Reference: @rinternals{TextScript}.
1181 @file{scm/@/define@/-markup@/-commands@/.scm}.
1185 @funindex \markuplines
1186 @code{\markuplines}.
1193 This section presents the way fonts are handled,
1194 and how they may be changed in scores.
1198 * Single entry fonts::
1199 * Entire document fonts::
1202 @node Fonts explained
1203 @unnumberedsubsubsec Fonts explained
1206 @cindex fonts, explained
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 A simpler, but more limited syntax is also described in
1235 @ref{Music notation inside markup}.
1237 Three families of text fonts are made available: the
1238 @emph{roman} (serif) font, that defaults to New Century
1239 Schoolbook, the @emph{sans} font and the monospaced
1240 @emph{typewriter} font -- these last two families are
1241 determined by the Pango installation.
1243 Each family may include different shapes and series.
1244 The following example demonstrates the ability to select
1245 alternate families, shapes, series and sizes. The value
1246 supplied to @code{font-size} is the required change from the
1249 @lilypond[quote,verbatim,relative=2]
1250 \override Score.RehearsalMark #'font-family = #'typewriter
1251 \mark \markup "Ouverture"
1252 \override Voice.TextScript #'font-shape = #'italic
1253 \override Voice.TextScript #'font-series = #'bold
1254 d2.^\markup "Allegro"
1255 \override Voice.TextScript #'font-size = #-3
1260 A similar syntax may be used in markup mode, however in this case
1261 it is preferable to use the simpler syntax explained in
1262 @ref{Selecting font and font size}:
1264 @lilypond[quote,verbatim]
1268 \override #'(font-shape . italic)
1269 \override #'(font-size . 4)
1273 \override #'(font-family . typewriter)
1275 \override #'(font-series . bold)
1279 \override #'(font-family . sans)
1286 Although it is easy to switch between preconfigured fonts,
1287 it is also possible to use other fonts, as explained in the
1288 following sections: @ref{Single entry fonts} and
1289 @ref{Entire document fonts}.
1294 @ref{The Feta font},
1295 @ref{Music notation inside markup},
1296 @ref{Selecting font and font size},
1300 @node Single entry fonts
1301 @unnumberedsubsubsec Single entry fonts
1303 Any font that is installed on the operating system and recognized
1304 by FontConfig may be used in a score, using the following syntax:
1306 @lilypond[quote,verbatim,relative=2]
1307 \override Staff.TimeSignature #'font-name = #"Charter"
1308 \override Staff.TimeSignature #'font-size = #2
1312 \override #'(font-name . "Vera Bold")
1317 @funindex show-available-fonts
1319 The following command displays a list of all available fonts
1320 on the operating system:
1323 lilypond -dshow-available-fonts x
1327 The last argument of the command can be anything, but has to be
1333 @ref{Fonts explained},
1334 @ref{Entire document fonts}.
1340 @file{lily/@/font@/-config@/-scheme@/.cc}.
1343 @node Entire document fonts
1344 @unnumberedsubsubsec Entire document fonts
1346 It is possible to change the fonts to be used as the default fonts in
1347 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1348 specifying them, in that order, as shown in the example below. For an
1349 explanation of fonts, see @ref{Fonts explained}.
1351 @cindex font families, setting
1352 @funindex make-pango-font-tree
1354 @lilypond[verbatim,quote]
1358 (make-pango-font-tree "Times New Roman"
1361 (/ myStaffSize 20)))
1368 \typewriter typewriter. }
1372 @c we don't do Helvetica / Courier, since GS incorrectly loads
1378 @ref{Fonts explained},
1379 @ref{Single entry fonts},
1380 @ref{Selecting font and font size},