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 Separate text blocks can be spread over multiple pages,
302 making it possible to print text documents or books entirely
303 within LilyPond. This feature, and the specific syntax it
304 requires, are described in @ref{Multi-page markup}.
309 @funindex \markuplines
315 TODO: add convenient snippets in input/new -vv
320 Notation Reference: @ref{Formatting text},
321 @ref{File structure},
322 @ref{Multiple scores in a book},
323 @ref{Multi-page markup}.
328 Internals Reference: @rinternals{TextScript}.
331 @node Formatting text
332 @subsection Formatting text
334 This section presents basic and advanced text formatting,
335 using the @code{\markup} mode specific syntax.
338 * Text markup introduction::
339 * Selecting font and font size::
341 * Graphic notation inside markup::
342 * Music notation inside markup::
343 * Multi-page markup::
346 @node Text markup introduction
347 @unnumberedsubsubsec Text markup introduction
355 A @code{\markup} block is used to typeset text with an extensible
356 syntax called @qq{markup mode}.
358 @cindex markup expressions
359 @cindex markup syntax
361 The markup syntax is similar to LilyPond's usual syntax: a
362 @code{\markup} expression is enclosed in curly braces @code{@{
363 @dots{} @}}. A single word is regarded as a minimal expression,
364 and therefore does not need to be enclosed with braces.
366 Unlike simple @qq{quoted text} indications, @code{\markup} blocks
367 may contain nested expressions or markup commands,
368 entered using the backslash @code{\} character.
369 Such commands only affect the first following expression.
371 @lilypond[quote,verbatim,fragment,relative=1]
373 a2^\markup { poco \italic più forte }
375 d2_\markup { \italic "string. assai" }
377 b1^\markup { \bold { molto \italic agitato } }
381 @cindex special characters in markup mode
382 @cindex markup mode, special characters
383 @cindex reserved characters, printing
384 @cindex printing special characters
385 @cindex quoted text in markup mode
387 A @code{\markup} block may also contain quoted text strings.
388 Such strings are treated as minimal text expressions, and
389 therefore any markup command or special character (such as
390 @code{\} and @code{#}) will be printed verbatim without affecting
391 the formatting of the text. Double quotation marks themselves
392 may be printed by preceding them with backslashes.
394 @lilypond[quote,verbatim,fragment,relative=1]
395 d1^"\italic markup..."
396 d_\markup { \italic "... prints \"italic\" letters!" }
400 To be treated as a distinct expression, a list of words needs
401 to be enclosed with double quotes or preceded by a command.
402 The way markup expressions are defined affects how these
403 expressions will be stacked, centered and aligned; in the
404 following example, the second @code{\markup} expression is
405 treated the same as the first one:
407 @lilypond[quote,verbatim,fragment,relative=1]
408 c1^\markup { \center-column { a bbb c } }
409 c1^\markup { \center-column { a { bbb c } } }
410 c1^\markup { \center-column { a \line { bbb c } } }
411 c1^\markup { \center-column { a "bbb c" } }
414 Markups can be stored in variables. Such variables may be
415 directly attached to notes:
417 @lilypond[quote,verbatim]
418 allegro = \markup { \bold \large Allegro }
428 An exhaustive list of @code{\markup}-specific commands can be found in
429 @ref{Text markup commands}.
435 @ref{Text markup commands}.
441 @file{scm/@/markup@/.scm}.
446 Syntax errors for markup mode can be confusing.
449 @node Selecting font and font size
450 @unnumberedsubsubsec Selecting font and font size
452 @cindex font switching
457 Basic font switching is supported in markup mode:
459 @lilypond[quote,verbatim,relative=2]
462 \italic { non troppo \underline Vivo }
465 d,_\markup { \italic quasi \smallCaps Tromba }
477 The size of the characters can also be altered in different ways:
480 the font size can be set to predefined standard sizes,
483 the font size can be set to an absolute value,
486 the font size can also be changed relatively to its previous value.
490 The following example demonstrates these three methods:
492 @lilypond[quote,verbatim,relative=1]
499 \fontsize #5 Sinfonia
506 \magnify #0.6 { e sentimento } )
516 Text may be printed as subscript or superscript. By default
517 these are printed in a smaller size, but a normal size can be used as well:
519 @lilypond[quote,verbatim]
522 \line { 1 \super st movement }
523 \line { 1 \normal-size-super st movement
524 \sub { (part two) } }
529 @cindex font families
531 The markup mode provides an easy way to select alternate
532 font families. The default serif font, of roman type, is
533 automatically selected unless specified otherwise; on the
534 last line of the following example, there is no difference
535 between the first and the second word.
537 @lilypond[quote,verbatim]
540 \line { Act \number 1 }
541 \line { \sans { Scene I. } }
542 \line { \typewriter { Verona. An open place. } }
543 \line { Enter \roman Valentine and Proteus. }
549 Some of these font families, used for specific items
550 such as numbers or dynamics, do not provide all
551 characters, as mentioned in @ref{New dynamic marks} and
552 @ref{Manual repeat marks}.
554 @c \concat is actually documented in Align (it is not
555 @c a font-switching command). But we need it here. -vv
557 When used inside a word, some font-switching or formatting
558 commands may produce an unwanted blank space. This can
559 easily be solved by concatenating the text elements together:
561 @lilypond[quote,verbatim]
565 \concat { 1 \super st }
569 \concat { \dynamic p , }
570 \italic { con dolce espressione }
576 An exhaustive list of font switching, and custom font usage
577 commands can be found in @ref{Font}.
579 Defining custom font sets is also possible, as explained in
587 @funindex \normalsize
604 @ref{New dynamic marks},
605 @ref{Manual repeat marks},
612 @rinternals{TextScript}.
615 @file{scm/@/define@/-markup@/-commands@/.scm}.
619 @unnumberedsubsubsec Text alignment
621 @cindex text, aligning
622 @cindex aligning text
624 This subsection discusses how to place text in markup mode.
625 Markup objects can also be moved as a whole, using the syntax
626 described in @rlearning{Moving objects}.
628 @c Padding commands should be mentioned on this page, but
629 @c most of these require \box to be more clearly illustrated. -vv
631 @cindex text, horizontal alignment
632 @cindex horizontal text alignment
633 @funindex \left-align
634 @funindex \center-align
635 @funindex \right-align
637 Markup objects may be aligned in different ways. By default,
638 a text indication is aligned on its left edge: in the following
639 example, there is no difference
640 between the first and the second markup.
642 @lilypond[quote,verbatim,fragment,relative=1]
645 d-\markup { \left-align poco }
647 d-\markup { \center-align { poco } }
649 d-\markup { \right-align poco }
654 Horizontal alignment may be fine-tuned
655 using a numeric value:
657 @lilypond[quote,verbatim,fragment,relative=1]
658 a1-\markup { \halign #-1 poco }
660 a,-\markup { \halign #0 poco }
662 a,-\markup { \halign #0.5 poco }
664 a,-\markup { \halign #2 poco }
668 Some objects may have alignment procedures of their own,
669 and therefore are not affected by these commands. It is
670 possible to move such markup objects as a whole, as shown
671 for instance in @ref{Text marks}.
673 @cindex text, vertical alignment
674 @cindex vertical text alignment
678 Vertical alignment is a bit more complex. As stated above,
679 markup objects can be moved as a whole; however, it is also
680 possible to move specific elements inside a markup block.
681 In this case, the element to be moved needs to be preceded
682 with an @emph{anchor point}, that can be another markup element
683 or an invisible object. The following example demonstrates these
684 two possibilities; the last markup in this example has no anchor
685 point, and therefore is not moved.
687 @lilypond[quote,verbatim,fragment,relative=1]
690 \raise #2 { Scène 1 }
695 \lower #4 \bold { Très modéré }
699 \raise #4 \italic { Une forêt. }
704 @funindex \general-align
706 @funindex \translate-scaled
708 Some commands can affect both the horizontal and vertical
709 alignment of text objects in markup mode. Any object
710 affected by these commands must be preceded with an
713 @lilypond[quote,verbatim,fragment,relative=1]
716 \translate #'(-1 . 2) "Scène 1"
721 \general-align #Y #3.2 \bold "Très modéré"
726 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
732 @funindex \center-column
734 @cindex multi-line markup
735 @cindex multi-line text
736 @cindex columns, text
738 A markup object may include several lines of text.
739 In the following example, each element or expression
740 is placed on its own line, either left-aligned or centered:
742 @lilypond[quote,verbatim]
760 @cindex centering text on the page
762 Similarly, a list of elements or expressions may be
763 spread to fill the entire horizontal line width (if there
764 is only one element, it will be centered on the page).
765 These expressions can, in turn, include multi-line text
766 or any other markup expression:
768 @lilypond[quote,verbatim]
771 \line { William S. Gilbert }
773 \huge \smallCaps "The Mikado"
775 \smallCaps "The Town of Titipu"
777 \line { Sir Arthur Sullivan }
788 @cindex wordwrapped text
789 @cindex justified text
791 Long text indications can also be automatically wrapped
792 accordingly to the given line width. These will be
793 either left-aligned or justified, as shown in
794 the following example.
796 @lilypond[quote,verbatim]
799 \line \smallCaps { La vida breve }
800 \line \bold { Acto I }
802 (La escena representa el corral de una casa de
803 gitanos en el AlbaicÃn de Granada. Al fondo una
804 puerta por la que se ve el negro interior de
805 una Fragua, iluminado por los rojos resplandores
810 \line \bold { Acto II }
811 \override #'(line-width . 50)
813 (Calle de Granada. Fachada de la casa de Carmela
814 y su hermano Manuel con grandes ventanas abiertas
815 a través de las que se ve el patio
816 donde se celebra una alegre fiesta)
822 An exhaustive list of text alignment commands
823 can be found in @ref{Align}.
827 @rlearning{Moving objects}.
836 Internals Reference: @rinternals{TextScript}.
839 @file{scm/@/define@/-markup@/-commands@/.scm}.
842 @node Graphic notation inside markup
843 @unnumberedsubsubsec Graphic notation inside markup
845 @cindex graphics, embedding
846 @cindex drawing graphic objects
848 Various graphic objects may be added to a score,
849 using markup commands.
853 @funindex \rounded-box
857 @cindex decorating text
860 Some markup commands allow decoration of text elements
861 with graphics, as demonstrated in the following example.
863 @lilypond[quote,verbatim]
872 \bracket "1866 - 1925"
875 \rounded-box \bold Prelude
880 @funindex \pad-markup
882 @funindex \pad-to-box
883 @funindex \pad-around
885 @cindex padding around text
888 Some commands may require an increase in the padding around
889 the text; this is achieved with some markup commands
890 exhaustively described in @ref{Align}.
892 @lilypond[quote,verbatim]
895 \box "Charles Ives (1874 - 1954)"
897 \box \pad-markup #2 "THE UNANSWERED QUESTION"
898 \box \pad-x #8 "A Cosmic Landscape"
905 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
906 \bold "Largo to Presto"
909 "String quartet keeps very even time,
910 Flute quartet keeps very uneven time."
915 @funindex \draw-circle
916 @funindex \filled-box
919 @funindex \arrow-head
921 @cindex graphic notation
922 @cindex symbols, non-musical
924 Other graphic elements or symbols may be printed
925 without requiring any text. As with any markup
926 expression, such objects can be combined.
928 @lilypond[quote,verbatim]
931 \draw-circle #4 #0.4 ##f
932 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
939 \arrow-head #Y #DOWN ##f
945 @funindex \postscript
947 @cindex embedded graphics
948 @cindex images, embedding
949 @cindex graphics, embedding
952 Advanced graphic features include the ability to
953 include external image files converted to the
954 Encapsulated PostScript format (@emph{eps}), or
955 to directly embed graphics into the input file,
956 using native PostScript code. In such a case, it
957 may be useful to explicitely specify the size of the
958 drawing, as demonstrated below:
960 @lilypond[quote,verbatim,fragment,relative=1]
963 \epsfile #X #10 #"./context-example.eps"
964 \with-dimensions #'(0 . 6) #'(0 . 10)
980 An exhaustive list of graphics-specific commands
981 can be found in @ref{Graphic}.
986 @ref{Editorial annotations}.
991 Internals Reference: @rinternals{TextScript}.
994 @file{scm/@/define@/-markup@/-commands@/.scm},
995 @file{scm/@/stencil@/.scm}.
997 @node Music notation inside markup
998 @unnumberedsubsubsec Music notation inside markup
1000 Various musical notation elements may be added
1001 to a score, inside a markup object.
1003 Notes and accidentals can be entered using markup
1006 @lilypond[quote,verbatim,fragment,relative=2]
1010 \note-by-number #1 #1 #1.5
1013 \natural \semiflat \flat
1014 \sesquiflat \doubleflat
1018 \natural \semisharp \sharp
1019 \sesquisharp \doublesharp
1024 Other notation objects may also be printed
1027 @lilypond[quote,verbatim,fragment,relative=1]
1034 fis_\markup { \dynamic rf }
1045 More generally, any available musical symbol may be
1046 included separately in a markup object, as demonstrated
1047 below; an exhaustive list of these symbols and their
1048 names can be found in @ref{The Feta font}.
1050 @lilypond[quote,verbatim,fragment,relative=2]
1052 c'^\markup { \musicglyph #"eight" }
1054 c,8._\markup { \musicglyph #"clefs.G_change" }
1056 c2^\markup { \musicglyph #"timesig.neomensural94" }
1058 @c TODO: add \lookup here? -vv
1061 Another way of printing non-text glyphs is described
1062 in @ref{Fonts explained}.
1064 The markup mode also supports diagrams for specific
1067 @lilypond[quote,verbatim,fragment,relative=2]
1069 \fret-diagram-terse #"x;x;o;2;3;2;"
1072 \harp-pedal #"^-v|--ov^"
1077 \musicglyph #"accordion.accDiscant"
1079 \raise #0.5 \musicglyph #"accordion.accDot"
1080 \raise #1.5 \musicglyph #"accordion.accDot"
1084 @c The accordion diagram is actually taken from a snippet.
1087 Such diagrams are documented in @ref{Instrument Specific Markup}.
1089 A whole score can even be nested inside a markup object.
1090 In such a case, the nested @code{\score} block must
1091 contain a @code{\layout} block, as demonstrated here:
1093 @lilypond[quote,verbatim,fragment,relative=1]
1096 \relative { c4 d e f }
1104 An exhaustive list of music notation related commands can be
1105 found in @ref{Music}.
1110 @ref{The Feta font},
1111 @ref{Fonts explained}.
1116 Internals Reference: @rinternals{TextScript}.
1119 @file{scm/@/define@/-markup@/-commands@/.scm},
1120 @file{scm/@/fret@/-diagrams@/.scm},
1121 @file{scm/@/harp@/-pedals@/.scm}.
1123 @node Multi-page markup
1124 @unnumberedsubsubsec Multi-page markup
1126 Although standard markup objects are not breakable, a
1127 specific syntax makes it possible to enter lines of text that can
1128 spread over multiple pages:
1130 @lilypond[quote,verbatim]
1133 A very long text of justified lines.
1137 An other very long paragraph.
1144 This syntax accepts a list of markups, that can be
1147 the result of a markup list command,
1151 a list of markup lists.
1154 An exhaustive list of markup list commands can be found in
1155 @ref{Text markup list commands}.
1159 @ref{Text markup list commands},
1160 @ref{New markup list command definition}.
1165 Internals Reference: @rinternals{TextScript}.
1168 @file{scm/@/define@/-markup@/-commands@/.scm}.
1171 @funindex \markuplines
1178 This section presents the way fonts are handled,
1179 and how they may be changed in scores.
1183 * Single entry fonts::
1184 * Entire document fonts::
1187 @node Fonts explained
1188 @unnumberedsubsubsec Fonts explained
1191 @cindex fonts, explained
1192 @funindex font-interface
1194 Fonts are handled through several libraries.
1195 FontConfig is used to detect available fonts on the system;
1196 the selected fonts are rendered using Pango.
1198 Music notation fonts can be described as a set of
1199 specific glyphs, ordered in several families.
1200 The following syntax allows to directly use various
1201 LilyPond @code{feta} non-text fonts in markup mode:
1203 @lilypond[quote,verbatim,fragment,relative=2]
1206 \override #'(font-encoding . fetaBraces)
1208 \override #'(font-encoding . fetaNumber)
1210 \override #'(font-encoding . fetaDynamic)
1212 \override #'(font-encoding . fetaMusic)
1213 \lookup #"noteheads.s0petrucci"
1219 A simpler, but more limited syntax is also described in
1220 @ref{Music notation inside markup}.
1222 Three families of text fonts are made available: the
1223 @emph{roman} (serif) font, that defaults to New Century
1224 Schoolbook, the @emph{sans} font and the monospaced
1225 @emph{typewriter} font -- these last two families are
1226 determined by the Pango installation.
1228 Each family may include different shapes and series.
1229 The following example demonstrates the ability to select
1230 alternate families, shapes, series and sizes:
1232 @lilypond[quote,verbatim,fragment,relative=2]
1233 \override Score.RehearsalMark #'font-family = #'typewriter
1234 \mark \markup "Ouverture"
1236 \override Voice.TextScript #'font-shape = #'italic
1237 \override Voice.TextScript #'font-series = #'bold
1238 d'2.^\markup "Allegro"
1243 A similar syntax may be used in markup mode, however in this case
1244 it is preferable to use the simpler syntax explained in
1245 @ref{Selecting font and font size}:
1247 @lilypond[quote,verbatim]
1251 \override #'(font-shape . italic)
1252 \override #'(font-size . 4)
1256 \override #'(font-family . typewriter)
1258 \override #'(font-series . bold)
1262 \override #'(font-family . sans)
1270 @c FIXME: This needs an example -vv
1272 The size of the font may be set with the @code{font-size}
1273 property. The resulting size is taken relative to the
1274 @code{text-font-size} as defined in the @code{\paper} block.
1277 Although it is easy to switch between preconfigured fonts,
1278 it is also possible to use other fonts, as explained in the
1279 following sections: @ref{Single entry fonts} and
1280 @ref{Entire document fonts}.
1284 @ref{The Feta font},
1285 @ref{Music notation inside markup},
1286 @ref{Selecting font and font size},
1289 @node Single entry fonts
1290 @unnumberedsubsubsec Single entry fonts
1292 Any font that is installed on the operating system and recognized
1293 by FontConfig may be used in a score, using the following syntax:
1295 @lilypond[quote,verbatim,fragment,relative=1]
1296 \override Staff.TimeSignature #'font-name = #"Charter"
1297 \override Staff.TimeSignature #'font-size = #2
1301 \override #'(font-name . "Vera Bold")
1306 @funindex show-available-fonts
1308 The following command displays a list of all available fonts
1309 on the operating system:
1312 lilypond -dshow-available-fonts x
1316 The last argument of the command can be anything, but has to be
1321 @ref{Fonts explained},
1322 @ref{Entire document fonts}.
1328 @file{lily/@/font@/-config@/-scheme@/.cc}.
1330 @node Entire document fonts
1331 @unnumberedsubsubsec Entire document fonts
1334 It is possible to change the default font families for the
1335 entire document. In such a case, the following syntax has
1336 to be used, by providing three font families that will be
1337 respectively used as @emph{roman}, @emph{sans} and @emph{typewriter}
1338 fonts, as explained in @ref{Fonts explained}.
1340 @cindex font families, setting
1341 @funindex make-pango-font-tree
1343 @lilypond[verbatim,quote]
1347 (make-pango-font-tree "Times New Roman"
1350 (/ myStaffSize 20)))
1357 \typewriter typewriter. }
1361 @c we don't do Helvetica / Courier, since GS incorrectly loads
1366 @ref{Fonts explained},
1367 @ref{Single entry fonts},
1368 @ref{Selecting font and font size},