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. For details, see the Contributors'
7 Guide, node Updating translation committishes..
15 @lilypondfile[quote]{text-headword.ly}
17 This section explains how to include text (with various
18 formatting) in music scores.
21 Some text elements that are not dealt with here are discussed in other
22 specific sections: @ref{Vocal music}, @ref{Titles and headers}.
31 @subsection Writing text
33 This section introduces different ways of adding text to a score.
35 @cindex Text, other languages
36 @warning{To write accented and special text (such as characters
37 from other languages), simply insert the characters directly into
38 the LilyPond file. The file must be saved as UTF-8. For more
39 information, see @ref{Text encoding}.}
50 @unnumberedsubsubsec Text scripts
53 @cindex text items, non-empty
54 @cindex non-empty texts
57 Simple @qq{quoted text} indications may be added to a score, as
58 demonstrated in the following example. Such indications may be
59 manually placed above or below the staff, using the syntax described
60 in @ref{Direction and placement}.
62 @lilypond[quote,verbatim,relative=2]
63 a8^"pizz." g f e a4-"scherz." f
66 This syntax is actually a shorthand; more complex text formatting may be
67 added to a note by explicitly using a @code{\markup} block, as described
68 in @ref{Formatting text}.
70 @lilypond[quote,verbatim,relative=2]
71 a8^\markup { \italic pizz. } g f e
72 a4_\markup { \tiny scherz. \bold molto } f
75 By default, text indications do not influence the note spacing. However,
76 their widths can be taken into account: in the following example, the
77 first text string does not affect spacing, whereas the second one does.
79 @lilypond[quote,verbatim,relative=2]
85 In addition to text scripts, articulations can be attached to notes.
86 For more information, see @ref{Articulations and ornamentations}.
88 For more information about the relative ordering of text scripts and
89 articulations, see @rlearning{Placement of objects}.
91 @funindex \textLengthOn
92 @funindex textLengthOn
93 @funindex \textLengthOff
94 @funindex textLengthOff
98 @code{\textLengthOff}.
104 @rlearning{Placement of objects}.
107 @ref{Formatting text},
108 @ref{Direction and placement},
109 @ref{Articulations and ornamentations}.
115 @rinternals{TextScript}.
118 @cindex text outside margin
119 @cindex margin, text running over
120 @cindex text, keeping inside margin
121 @cindex lyrics, keeping inside margin
125 Checking to make sure that text scripts and lyrics are within the
126 margins is a relatively large computational task. To speed up
127 processing, LilyPond does not perform such calculations by
128 default; to enable it, use
131 \override Score.PaperColumn #'keep-inside-line = ##t
136 @unnumberedsubsubsec Text spanners
138 @cindex text spanners
140 Some performance indications, e.g., @notation{rallentando} or
141 @notation{accelerando}, are written as text and are extended over
142 multiple notes with dotted lines. Such objects, called
143 @qq{spanners}, may be created from one note to another using the
146 @lilypond[verbatim,quote,relative=2]
147 \override TextSpanner #'(bound-details left text) = "rit."
152 @cindex text spanners, formatting
153 @cindex formatting text spanners
156 The string to be printed is set through object properties. By default
157 it is printed in italic characters, but different formatting can be
158 obtained using @code{\markup} blocks, as described in
159 @ref{Formatting text}.
161 @lilypond[quote,relative=2,verbatim]
162 \override TextSpanner #'(bound-details left text) =
163 \markup { \upright "rit." }
168 The line style, as well as the text string, can be defined as an
169 object property. This syntax is described in @ref{Line styles}.
171 @funindex \textSpannerUp
172 @funindex textSpannerUp
173 @funindex \textSpannerDown
174 @funindex textSpannerDown
175 @funindex \textSpannerNeutral
176 @funindex textSpannerNeutral
180 @code{\textSpannerUp},
181 @code{\textSpannerDown},
182 @code{\textSpannerNeutral}.
186 LilyPond is only able to handle one text spanner per voice.
190 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
191 {dynamics-text-spanner-postfix.ly}
193 @lilypondfile[verbatim,lilyquote,texidoc,doctitle]
194 {dynamics-custom-text-spanner-postfix.ly}
200 @ref{Formatting text}.
204 @rlsr{Expressive marks}.
207 @rinternals{TextSpanner}.
211 @unnumberedsubsubsec Text marks
216 @cindex text on bar line
217 @cindex coda on bar line
218 @cindex segno on bar line
219 @cindex fermata on bar line
220 @cindex bar lines, symbols on
227 Various text elements may be added to a score using the syntax described
228 in @ref{Rehearsal marks}:
230 @c \mark needs to be placed on a separate line (it's not
231 @c attached to an object like \markup is). -vv
233 @lilypond[verbatim,quote,relative=2]
239 This syntax makes it possible to put any text on a bar line;
240 more complex text formatting may be added using a @code{\markup}
241 block, as described in @ref{Formatting text}:
243 @lilypond[quote,verbatim,relative=1]
245 \mark \markup { \italic { colla parte } }
251 This syntax also allows to print special signs, like coda, segno
252 or fermata, by specifying the appropriate symbol name as explained in
253 @ref{Music notation inside markup}:
255 @lilypond[quote,verbatim,relative=2]
257 \mark \markup { \musicglyph #"scripts.ufermata" }
262 Such objects are only typeset above the top staff of the score;
263 depending on whether they are specified at the end or the middle of a
264 bar, they can be placed above the bar line or between notes. When
265 specified at a line break, the mark will be printed at the beginning of
268 @lilypond[quote,verbatim,relative=2]
278 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
279 {printing-marks-at-the-end-of-a-line.ly}
281 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
282 {aligning-marks-with-various-notation-objects.ly}
284 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
285 {printing-marks-on-every-staff.ly}
290 @ref{Rehearsal marks},
291 @ref{Formatting text},
292 @ref{Music notation inside markup},
299 @rinternals{MarkEvent},
300 @rinternals{Mark_engraver},
301 @rinternals{RehearsalMark}.
305 @unnumberedsubsubsec Separate text
307 @cindex separate text
308 @cindex text, separate
309 @cindex standalone text
310 @cindex top-level text
311 @cindex text, top-level
312 @cindex text, standalone
317 A @code{\markup} block can exist by itself, outside of any
318 @code{\score} block, as a @qq{top-level expression}. This syntax
319 is described in @ref{File structure}.
321 @lilypond[verbatim,quote]
323 Tomorrow, and tomorrow, and tomorrow...
328 This allows printing text separately from the music, which is
329 particularly useful when the input file contains several music pieces,
330 as described in @ref{Multiple scores in a book}.
332 @lilypond[quote,verbatim]
337 Tomorrow, and tomorrow, and tomorrow...
344 Separate text blocks can be spread over multiple pages,
345 making it possible to print text documents or books entirely
346 within LilyPond. This feature, and the specific syntax it
347 requires, are described in @ref{Multi-page markup}.
352 @funindex \markuplines
353 @funindex markuplines
363 @lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
364 {stand-alone-two-column-markup.ly}
369 @ref{Formatting text},
370 @ref{File structure},
371 @ref{Multiple scores in a book},
372 @ref{Multi-page markup}.
378 @rinternals{TextScript}.
381 @node Formatting text
382 @subsection Formatting text
384 This section presents basic and advanced text formatting,
385 using the @code{\markup} mode specific syntax.
388 * Text markup introduction::
389 * Selecting font and font size::
391 * Graphic notation inside markup::
392 * Music notation inside markup::
393 * Multi-page markup::
396 @node Text markup introduction
397 @unnumberedsubsubsec Text markup introduction
407 A @code{\markup} block is used to typeset text with an extensible
408 syntax called @qq{markup mode}.
410 @cindex markup expressions
411 @cindex expressions, markup
412 @cindex markup syntax
413 @cindex syntax, markup
415 The markup syntax is similar to LilyPond's usual syntax: a
416 @code{\markup} expression is enclosed in curly braces
417 @code{@{@dots{} @}}. A single word is regarded as a minimal expression,
418 and therefore does not need to be enclosed with braces.
420 Unlike simple @qq{quoted text} indications, @code{\markup} blocks may
421 contain nested expressions or markup commands, entered using the
422 backslash @code{\} character. Such commands only affect the first
423 following expression.
425 @lilypond[quote,verbatim,relative=2]
427 a2^\markup { poco \italic più forte }
429 d2_\markup { \italic "string. assai" }
431 b1^\markup { \bold { molto \italic agitato } }
435 @cindex special characters in markup mode
436 @cindex markup mode, special characters
437 @cindex reserved characters, printing
438 @cindex printing reserved characters
439 @cindex printing special characters
440 @cindex quoted text in markup mode
441 @cindex markup mode, quoted text
443 A @code{\markup} block may also contain quoted text strings. Such
444 strings are treated as minimal text expressions, and therefore any
445 markup command or special character (such as @code{\} and @code{#})
446 will be printed verbatim without affecting the formatting of the text.
447 Double quotation marks themselves may be printed by preceding them
450 @lilypond[quote,verbatim,relative=2]
451 a1^"\italic markup..."
452 a_\markup { \italic "... prints \"italic\" letters!" }
456 To be treated as a distinct expression, a list of words needs to be
457 enclosed with double quotes or preceded by a command. The way markup
458 expressions are defined affects how these expressions will be stacked,
459 centered and aligned; in the following example, the second
460 @code{\markup} expression is treated the same as the first one:
462 @lilypond[quote,verbatim,relative=2]
463 c1^\markup { \center-column { a bbb c } }
464 c1^\markup { \center-column { a { bbb c } } }
465 c1^\markup { \center-column { a \line { bbb c } } }
466 c1^\markup { \center-column { a "bbb c" } }
469 Markups can be stored in variables. Such variables may be
470 directly attached to notes:
472 @lilypond[quote,verbatim]
473 allegro = \markup { \bold \large Allegro }
483 An exhaustive list of @code{\markup}-specific commands can be found in
484 @ref{Text markup commands}.
489 @ref{Text markup commands}.
495 @file{scm/markup.scm}.
499 Syntax errors for markup mode can be confusing.
502 @node Selecting font and font size
503 @unnumberedsubsubsec Selecting font and font size
505 @cindex font switching
506 @cindex changing fonts
507 @cindex switching fonts
516 Basic font switching is supported in markup mode:
518 @lilypond[quote,verbatim,relative=2]
521 \italic { non troppo \underline Vivo }
524 d,_\markup { \italic quasi \smallCaps Tromba }
540 The size of the characters can also be altered in different ways:
543 the font size can be set to predefined standard sizes,
546 the font size can be set to an absolute value,
549 the font size can also be changed relatively to its previous value.
553 The following example demonstrates these three methods:
555 @lilypond[quote,verbatim,relative=1]
562 \fontsize #5 Sinfonia
569 \magnify #0.6 { e sentimento } )
582 Text may be printed as subscript or superscript. By default these are
583 printed in a smaller size, but a normal size can be used as well:
585 @lilypond[quote,verbatim]
588 \line { 1 \super st movement }
589 \line { 1 \normal-size-super st movement
590 \sub { (part two) } }
595 @cindex font families
597 The markup mode provides an easy way to select alternate font
598 families. The default serif font, of roman type, is automatically
599 selected unless specified otherwise; on the last line of the following
600 example, there is no difference between the first and the second word.
602 @lilypond[quote,verbatim]
605 \line { Act \number 1 }
606 \line { \sans { Scene I. } }
607 \line { \typewriter { Verona. An open place. } }
608 \line { Enter \roman Valentine and Proteus. }
614 Some of these font families, used for specific items such as numbers
615 or dynamics, do not provide all characters, as mentioned in
616 @ref{New dynamic marks} and @ref{Manual repeat marks}.
618 @c \concat is actually documented in Align (it is not
619 @c a font-switching command). But we need it here. -vv
621 When used inside a word, some font-switching or formatting commands
622 may produce an unwanted blank space. This can easily be solved by
623 concatenating the text elements together:
625 @lilypond[quote,verbatim]
629 \concat { 1 \super st }
633 \concat { \dynamic p , }
634 \italic { con dolce espressione }
640 An exhaustive list of font switching commands and custom font usage
641 commands can be found in @ref{Font}.
643 Defining custom font sets is also possible, as explained in
652 @funindex \normalsize
679 @ref{New dynamic marks},
680 @ref{Manual repeat marks},
687 @rinternals{TextScript}.
690 @file{scm/define-markup-commands.scm}.
693 Using the font sizing commands @code{\teeny}, @code{\tiny},
694 @code{\small}, @code{\normalsize}, @code{\large}, and
695 @code{\huge} will lead to inconsistent line spacing compared to
696 using @code{\fontsize}.
700 @unnumberedsubsubsec Text alignment
702 @cindex text, aligning
703 @cindex aligning text
704 @cindex aligning markup text
705 @cindex aligning markups
706 @cindex markups, aligning
707 @cindex markup text, aligning
709 This subsection discusses how to place text in markup mode. Markup
710 objects can also be moved as a whole, using the syntax described in
711 @rlearning{Moving objects}.
713 @c Padding commands should be mentioned on this page, but
714 @c most of these require \box to be more clearly illustrated. -vv
716 @cindex text, horizontal alignment
717 @cindex horizontal text alignment
719 @funindex \left-align
721 @funindex \center-align
722 @funindex center-align
723 @funindex \right-align
724 @funindex right-align
726 Markup objects may be aligned in different ways. By default, a text
727 indication is aligned on its left edge: in the following example,
728 there is no difference between the first and the second markup.
730 @lilypond[quote,verbatim,relative=2]
733 d-\markup { \left-align poco }
735 d-\markup { \center-align { poco } }
737 d-\markup { \right-align poco }
743 Horizontal alignment may be fine-tuned using a numeric value:
745 @lilypond[quote,verbatim,relative=2]
746 a1-\markup { \halign #-1 poco }
748 a,-\markup { \halign #0 poco }
750 a,-\markup { \halign #0.5 poco }
752 a,-\markup { \halign #2 poco }
756 Some objects may have alignment procedures of their own, and therefore
757 are not affected by these commands. It is possible to move such
758 markup objects as a whole, as shown for instance in
761 @cindex text, vertical alignment
762 @cindex vertical text alignment
771 @c QUERY Should the function of ``\null'' be clarified? rp
773 Vertical alignment is a bit more complex. As stated above, markup
774 objects can be moved as a whole; however, it is also possible to move
775 specific elements inside a markup block. In this case, the element to
776 be moved needs to be preceded with an @emph{anchor point}, that can be
777 another markup element or an invisible object. The following example
778 demonstrates these two possibilities; the last markup in this example
779 has no anchor point, and therefore is not moved.
781 @lilypond[quote,verbatim,relative=1]
784 \raise #2 { Scène 1 }
789 \lower #4 \bold { Très modéré }
793 \raise #4 \italic { Une forêt. }
798 @funindex \general-align
799 @funindex general-align
802 @funindex \translate-scaled
803 @funindex translate-scaled
805 Some commands can affect both the horizontal and vertical alignment of
806 text objects in markup mode. Any object affected by these commands
807 must be preceded with an anchor point:
809 @lilypond[quote,verbatim,relative=1]
812 \translate #'(-1 . 2) "Scène 1"
817 \general-align #Y #3.2 \bold "Très modéré"
822 \translate-scaled #'(-1 . 2) \teeny "Une forêt."
827 @cindex multi-line markup
828 @cindex markup, multi-line
829 @cindex multi-line text
830 @cindex text, multi-line
831 @cindex text in columns
832 @cindex columns, text
836 @funindex \center-column
837 @funindex center-column
839 A markup object may include several lines of text. In the following
840 example, each element or expression is placed on its own line, either
841 left-aligned or centered:
843 @lilypond[quote,verbatim]
859 @cindex centering text on the page
860 @cindex text, centering on the page
861 @cindex markup, centering on the page
866 Similarly, a list of elements or expressions may be spread to fill the
867 entire horizontal line width (if there is only one element, it will be
868 centered on the page). These expressions can, in turn, include
869 multi-line text or any other markup expression:
871 @lilypond[quote,verbatim]
874 \line { William S. Gilbert }
876 \huge \smallCaps "The Mikado"
878 \smallCaps "The Town of Titipu"
880 \line { Sir Arthur Sullivan }
888 @cindex wordwrapped text
889 @cindex justified text
890 @cindex text, justified
891 @cindex text, wordwrapped
892 @cindex markup text, wordwrapped
893 @cindex markup text, justified
900 Long text indications can also be automatically wrapped accordingly to
901 the given line width. These will be either left-aligned or justified,
902 as shown in the following example.
904 @lilypond[quote,verbatim]
907 \line \smallCaps { La vida breve }
908 \line \bold { Acto I }
910 (La escena representa el corral de una casa de
911 gitanos en el AlbaicÃn de Granada. Al fondo una
912 puerta por la que se ve el negro interior de
913 una Fragua, iluminado por los rojos resplandores
918 \line \bold { Acto II }
919 \override #'(line-width . 50)
921 (Calle de Granada. Fachada de la casa de Carmela
922 y su hermano Manuel con grandes ventanas abiertas
923 a través de las que se ve el patio
924 donde se celebra una alegre fiesta)
930 @cindex text alignment commands
931 @cindex markup text alignment commands
932 @cindex alignment, text, commands
934 An exhaustive list of text alignment commands can be found in
940 @rlearning{Moving objects}.
950 @rinternals{TextScript}.
953 @file{scm/define-markup-commands.scm}.
956 @node Graphic notation inside markup
957 @unnumberedsubsubsec Graphic notation inside markup
959 @cindex graphics, embedding
960 @cindex drawing graphic objects
961 @cindex graphic objects, drawing
962 @cindex embedding graphic objects
963 @cindex graphic objects, embedding
965 Various graphic objects may be added to a score, using markup
968 @cindex decorating text
970 @cindex text, framing
971 @cindex text, decorating
972 @cindex markup text, decorating
973 @cindex markup text, framing
979 @funindex \rounded-box
980 @funindex rounded-box
986 Some markup commands allow decoration of text elements with graphics,
987 as demonstrated in the following example.
989 @lilypond[quote,verbatim]
998 \bracket "1866 - 1925"
1001 \rounded-box \bold Prelude
1006 @cindex padding around text
1007 @cindex text padding
1008 @cindex markup text padding
1010 @funindex \pad-markup
1011 @funindex pad-markup
1014 @funindex \pad-to-box
1015 @funindex pad-to-box
1016 @funindex \pad-around
1017 @funindex pad-around
1019 Some commands may require an increase in the padding around the text;
1020 this is achieved with some markup commands exhaustively described in
1023 @lilypond[quote,verbatim]
1024 \markup \fill-line {
1026 \box "Charles Ives (1874 - 1954)"
1028 \box \pad-markup #2 "THE UNANSWERED QUESTION"
1029 \box \pad-x #8 "A Cosmic Landscape"
1036 \box \pad-to-box #'(-5 . 20) #'(0 . 5)
1037 \bold "Largo to Presto"
1040 "String quartet keeps very even time,
1041 Flute quartet keeps very uneven time."
1045 @cindex graphic notation
1046 @cindex symbols, non-musical
1047 @cindex non-musical symbols
1048 @cindex notation, graphic
1052 @funindex \draw-circle
1053 @funindex draw-circle
1054 @funindex \filled-box
1055 @funindex filled-box
1058 @funindex \draw-line
1060 @funindex \arrow-head
1061 @funindex arrow-head
1063 Other graphic elements or symbols may be printed without requiring any
1064 text. As with any markup expression, such objects can be combined.
1066 @lilypond[quote,verbatim]
1069 \draw-circle #4 #0.4 ##f
1070 \filled-box #'(-4 . 4) #'(-0.5 . 0.5) #1
1076 \draw-line #'(0 . 4)
1077 \arrow-head #Y #DOWN ##f
1082 @cindex embedded graphics
1083 @cindex images, embedding
1084 @cindex graphics, embedding
1089 @funindex \postscript
1090 @funindex postscript
1092 Advanced graphic features include the ability to include external
1093 image files converted to the Encapsulated PostScript format
1094 (@emph{eps}), or to directly embed graphics into the input file, using
1095 native PostScript code. In such a case, it may be useful to
1096 explicitly specify the size of the drawing, as demonstrated below:
1098 @lilypond[quote,verbatim,relative=1]
1101 \epsfile #X #10 #"./context-example.eps"
1102 \with-dimensions #'(0 . 6) #'(0 . 10)
1118 An exhaustive list of graphics-specific commands can be found in
1125 @ref{Editorial annotations},
1131 Internals Reference:
1132 @rinternals{TextScript}.
1135 @file{scm/define-markup-commands.scm},
1136 @file{scm/stencil.scm}.
1139 @node Music notation inside markup
1140 @unnumberedsubsubsec Music notation inside markup
1142 @cindex notation inside markup
1143 @cindex music inside markup
1144 @cindex markup, music notation inside
1146 Various musical notation elements may be added to a score, inside a
1149 Notes and accidentals can be entered using markup commands:
1151 @lilypond[quote,verbatim,relative=2]
1155 \note-by-number #1 #1 #1.5
1158 \natural \semiflat \flat
1159 \sesquiflat \doubleflat
1163 \natural \semisharp \sharp
1164 \sesquisharp \doublesharp
1169 Other notation objects may also be printed
1172 @lilypond[quote,verbatim,relative=1]
1179 fis_\markup { \dynamic rf }
1190 More generally, any available musical symbol may be included
1191 separately in a markup object, as demonstrated below; an exhaustive
1192 list of these symbols and their names can be found in
1193 @ref{The Feta font}.
1195 @lilypond[quote,verbatim,relative=2]
1197 c'^\markup { \musicglyph #"eight" }
1199 c,8._\markup { \musicglyph #"clefs.G_change" }
1201 c2^\markup { \musicglyph #"timesig.neomensural94" }
1204 Another way of printing non-text glyphs is described in
1205 @ref{Fonts explained}. This is useful for printing braces of various
1208 The markup mode also supports diagrams for specific
1211 @lilypond[quote,verbatim,relative=2]
1213 \fret-diagram-terse #"x;x;o;2;3;2;"
1216 \harp-pedal #"^-v|--ov^"
1221 \musicglyph #"accordion.discant"
1223 \raise #0.5 \musicglyph #"accordion.dot"
1224 \raise #1.5 \musicglyph #"accordion.dot"
1228 @c The accordion diagram is actually taken from a snippet.
1231 Such diagrams are documented in @ref{Instrument Specific Markup}.
1233 @cindex score inside markup
1234 @cindex markup, score inside
1236 A whole score can even be nested inside a markup object. In such a
1237 case, the nested @code{\score} block must contain a @code{\layout}
1238 block, as demonstrated here:
1240 @lilypond[quote,verbatim,relative=1]
1243 \relative c' { c4 d e f }
1251 An exhaustive list of music notation related commands can be found in
1258 @ref{The Feta font},
1259 @ref{Fonts explained}.
1264 Internals Reference:
1265 @rinternals{TextScript}.
1268 @file{scm/define-markup-commands.scm},
1269 @file{scm/fret-diagrams.scm},
1270 @file{scm/harp-pedals.scm}.
1273 @node Multi-page markup
1274 @unnumberedsubsubsec Multi-page markup
1276 @cindex multi-page markup
1277 @cindex markup, multi-page
1278 @cindex markup text, multi-page
1279 @cindex text spread over multiple pages
1281 @funindex \markuplines
1282 @funindex markuplines
1283 @funindex \justified-lines
1284 @funindex justified-lines
1285 @funindex \wordwrap-lines
1286 @funindex wordwrap-lines
1288 Although standard markup objects are not breakable, a specific syntax
1289 makes it possible to enter lines of text that can spread over multiple
1292 @lilypond[quote,verbatim]
1295 A very long text of justified lines.
1299 Another very long paragraph.
1306 This syntax accepts a list of markups, that can be
1309 the result of a markup list command,
1313 a list of markup lists.
1316 An exhaustive list of markup list commands can be found in
1317 @ref{Text markup list commands}.
1322 @ref{Text markup list commands},
1328 @rextend{New markup list command definition}.
1330 Internals Reference:
1331 @rinternals{TextScript}.
1334 @file{scm/define-markup-commands.scm}.
1337 @funindex \markuplines
1338 @funindex markuplines
1341 @code{\markuplines}.
1348 This section presents the way fonts are handled, and how they may be
1353 * Single entry fonts::
1354 * Entire document fonts::
1357 @node Fonts explained
1358 @unnumberedsubsubsec Fonts explained
1361 @cindex fonts, explained
1362 @cindex braces, various sizes
1363 @cindex fonts, non-text in markup
1364 @cindex non-text fonts in markup
1366 @funindex font-interface
1368 Fonts are handled through several libraries. FontConfig is used to
1369 detect available fonts on the system; the selected fonts are rendered
1372 Music notation fonts can be described as a set of specific glyphs,
1373 ordered in several families. The following syntax allows various
1374 LilyPond @code{feta} non-text fonts to be used directly in markup
1377 @lilypond[quote,verbatim,relative=2]
1380 \override #'(font-encoding . fetaBraces)
1382 \override #'(font-encoding . fetaText)
1384 \override #'(font-encoding . fetaMusic)
1385 \lookup #"noteheads.s0petrucci"
1391 However, all these glyphs except the braces of various sizes contained
1392 in @code{fetaBraces} are available using the simpler syntax described
1393 in @ref{Music notation inside markup}.
1395 When using the glyphs contained in @code{fetaBraces}, the size of the
1396 brace is specified by the numerical part of the glyph name, in
1397 arbitrary units. Any integer from @code{0} to @code{575} inclusive
1398 may be specified, @code{0} giving the smallest brace. The optimum
1399 value must be determined by trial and error. These glyphs are all
1400 left braces; right braces may be obtained by rotation, see
1401 @ref{Rotating objects}.
1403 Three families of text fonts are made available: the @emph{roman}
1404 (serif) font, that defaults to New Century Schoolbook, the
1405 @emph{sans} font and the monospaced @emph{typewriter} font -- these
1406 last two families are determined by the Pango installation.
1408 Each family may include different shapes and series. The following
1409 example demonstrates the ability to select alternate families, shapes,
1410 series and sizes. The value supplied to @code{font-size} is the
1411 required change from the default size.
1413 @lilypond[quote,verbatim,relative=2]
1414 \override Score.RehearsalMark #'font-family = #'typewriter
1415 \mark \markup "Ouverture"
1416 \override Voice.TextScript #'font-shape = #'italic
1417 \override Voice.TextScript #'font-series = #'bold
1418 d2.^\markup "Allegro"
1419 \override Voice.TextScript #'font-size = #-3
1424 A similar syntax may be used in markup mode; however in this case it
1425 is preferable to use the simpler syntax explained in
1426 @ref{Selecting font and font size}:
1428 @lilypond[quote,verbatim]
1432 \override #'(font-shape . italic)
1433 \override #'(font-size . 4)
1437 \override #'(font-family . typewriter)
1439 \override #'(font-series . bold)
1443 \override #'(font-family . sans)
1450 Although it is easy to switch between preconfigured fonts, it is also
1451 possible to use other fonts, as explained in the following sections:
1452 @ref{Single entry fonts} and @ref{Entire document fonts}.
1457 @ref{The Feta font},
1458 @ref{Music notation inside markup},
1459 @ref{Rotating objects},
1460 @ref{Selecting font and font size},
1464 @node Single entry fonts
1465 @unnumberedsubsubsec Single entry fonts
1467 Any font that is installed on the operating system and recognized by
1468 FontConfig may be used in a score, using the following syntax:
1470 @lilypond[quote,verbatim,relative=2]
1471 \override Staff.TimeSignature #'font-name = #"Bitstream Charter"
1472 \override Staff.TimeSignature #'font-size = #2
1476 \override #'(font-name . "Vera Bold")
1481 @cindex fonts, finding available
1482 @cindex finding available fonts
1483 @cindex listing available fonts
1484 @cindex available fonts, listing
1486 @funindex show-available-fonts
1488 The following command displays a list of all available fonts on the
1492 lilypond -dshow-available-fonts x
1498 @ref{Fonts explained},
1499 @ref{Entire document fonts}.
1504 @c A source file gets never installed...
1506 @c @file{lily/font-config-scheme.cc}.
1509 @node Entire document fonts
1510 @unnumberedsubsubsec Entire document fonts
1512 It is possible to change the fonts to be used as the default fonts in
1513 the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
1514 specifying them, in that order, as shown in the example below. For an
1515 explanation of fonts, see @ref{Fonts explained}.
1517 @cindex font families, setting
1518 @cindex fonts, changing for entire document
1520 @funindex make-pango-font-tree
1522 @lilypond[verbatim,quote]
1526 (make-pango-font-tree "Times New Roman"
1529 (/ myStaffSize 20)))
1536 \typewriter typewriter. }
1540 @c we don't do Helvetica / Courier, since GS incorrectly loads
1546 @ref{Fonts explained},
1547 @ref{Single entry fonts},
1548 @ref{Selecting font and font size},