Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
When revising a translation, copy the HEAD committish of the
- version that you are working on. See TRANSLATION for details.
+ version that you are working on. For details, see the Contributors'
+ Guide, node Updating translation committishes..
@end ignore
-@c \version "2.12.0"
+@c \version "2.17.6"
@node Text
@section Text
a8^"pizz." g f e a4-"scherz." f
@end lilypond
-This syntax is actually a shorthand; more complex text
-formatting may be added to a note by explicitly using a
-@code{\markup} block, as described in @ref{Formatting text}.
+This syntax is actually a shorthand; more complex text formatting may be
+added to a note by explicitly using a @code{\markup} block, as described
+in @ref{Formatting text}.
@lilypond[quote,verbatim,relative=2]
a8^\markup { \italic pizz. } g f e
a4_\markup { \tiny scherz. \bold molto } f
@end lilypond
-By default, text indications do not influence the note spacing.
-However, their widths can be taken into account:
-in the following example, the first text string does not affect
-spacing, whereas the second one does.
+By default, text indications do not influence the note spacing. However,
+their widths can be taken into account: in the following example, the
+first text string does not affect spacing, whereas the second one does.
@lilypond[quote,verbatim,relative=2]
a8^"pizz." g f e
a4_"scherzando" f
@end lilypond
+In addition to text scripts, articulations can be attached to notes.
+For more information, see @ref{Articulations and ornamentations}.
+
+For more information about the relative ordering of text scripts and
+articulations, see @rlearning{Placement of objects}.
@funindex \textLengthOn
@funindex textLengthOn
@code{\textLengthOff}.
@endpredefined
-
@seealso
+Learning Manual:
+@rlearning{Placement of objects}.
+
Notation Reference:
@ref{Formatting text},
-@ref{Direction and placement}.
+@ref{Direction and placement},
+@ref{Articulations and ornamentations}.
Snippets:
@rlsr{Text}.
Internals Reference:
@rinternals{TextScript}.
-
@cindex text outside margin
@cindex margin, text running over
@cindex text, keeping inside margin
@cindex lyrics, keeping inside margin
-
@knownissues
-
Checking to make sure that text scripts and lyrics are within the
-margins is a relatively large computational task. To speed up
-processing, LilyPond does not perform such calculations by
-default; to enable it, use
+margins requires additonal calculations. In cases where slightly faster
+performance is desired, use
@example
-\override Score.PaperColumn #'keep-inside-line = ##t
+\override Score.PaperColumn.keep-inside-line = ##f
@end example
Some performance indications, e.g., @notation{rallentando} or
@notation{accelerando}, are written as text and are extended over
-multiple notes with dotted lines. Such objects, called @qq{spanners},
-may be created from one note to another using the following syntax:
+multiple notes with dotted lines. Such objects, called
+@qq{spanners}, may be created from one note to another using the
+following syntax:
@lilypond[verbatim,quote,relative=2]
-\override TextSpanner #'(bound-details left text) = "rit."
+\override TextSpanner.bound-details.left.text = "rit."
b1\startTextSpan
e,\stopTextSpan
@end lilypond
@noindent
The string to be printed is set through object properties. By default
it is printed in italic characters, but different formatting can be
-obtained using @code{\markup} blocks, as described in @ref{Formatting
-text}.
+obtained using @code{\markup} blocks, as described in
+@ref{Formatting text}.
@lilypond[quote,relative=2,verbatim]
-\override TextSpanner #'(bound-details left text) =
+\override TextSpanner.bound-details.left.text =
\markup { \upright "rit." }
b1\startTextSpan c
e,\stopTextSpan
The line style, as well as the text string, can be defined as an
object property. This syntax is described in @ref{Line styles}.
-
@funindex \textSpannerUp
@funindex textSpannerUp
@funindex \textSpannerDown
@code{\textSpannerNeutral}.
@endpredefined
+@knownissues
+LilyPond is only able to handle one text spanner per voice.
+
+@snippets
+
+@lilypondfile[verbatim,quote,texidoc,doctitle]
+{dynamics-text-spanner-postfix.ly}
+
+@lilypondfile[verbatim,quote,texidoc,doctitle]
+{dynamics-custom-text-spanner-postfix.ly}
@seealso
Notation Reference:
@ref{Line styles},
-@ref{Dynamics}.
+@ref{Dynamics},
+@ref{Formatting text}.
Snippets:
-@rlsr{Text}.
+@rlsr{Text},
+@rlsr{Expressive marks}.
Internals Reference:
@rinternals{TextSpanner}.
@funindex \markup
@funindex markup
-Various text elements may be added to a score using
-the syntax described in @ref{Rehearsal marks}:
+Various text elements may be added to a score using the syntax described
+in @ref{Rehearsal marks}:
@c \mark needs to be placed on a separate line (it's not
@c attached to an object like \markup is). -vv
@end lilypond
@noindent
-Such objects are only typeset above the top staff of the score; depending on
-whether they are specified at the end or the middle of a bar, they
-can be placed above the bar line or between notes. When specified at a
-line break, the mark will be printed at the beginning of the next line.
+Such objects are only typeset above the top staff of the score;
+depending on whether they are specified at the end or the middle of a
+bar, they can be placed above the bar line or between notes. When
+specified at a line break, the mark will be printed at the beginning of
+the next line.
@lilypond[quote,verbatim,relative=2]
\mark "Allegro"
@snippets
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
-{printing-marks-at-the-end-of-a-line-or-a-score.ly}
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
+{printing-marks-at-the-end-of-a-line.ly}
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{aligning-marks-with-various-notation-objects.ly}
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{printing-marks-on-every-staff.ly}
-
@seealso
Notation Reference:
@ref{Rehearsal marks},
@rlsr{Text}.
Internals Reference:
+@rinternals{MarkEvent},
+@rinternals{Mark_engraver},
@rinternals{RehearsalMark}.
-@knownissues
-@c To be removed when Issue 69 in the tracker gets fixed. -vv
-
-If a mark is entered at the end of the last bar of the score (where
-there is no next line), then the mark will not be printed at
-all.
-
@node Separate text
@unnumberedsubsubsec Separate text
@funindex markup
A @code{\markup} block can exist by itself, outside of any
-any @code{\score} block, as a @qq{top-level
-expression}. This syntax is described in @ref{File structure}.
+@code{\score} block, as a @qq{top-level expression}. This syntax
+is described in @ref{File structure}.
@lilypond[verbatim,quote]
\markup {
@funindex \markup
@funindex markup
-@funindex \markuplines
-@funindex markuplines
+@funindex \markuplist
+@funindex markuplist
@predefined
@code{\markup},
-@code{\markuplines}.
+@code{\markuplist}.
@endpredefined
@snippets
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+@lilypondfile[verbatim,quote,ragged-right,texidoc,doctitle]
{stand-alone-two-column-markup.ly}
-
@seealso
Notation Reference:
@ref{Formatting text},
@cindex markup expressions
@cindex expressions, markup
@cindex markup syntax
-@cindex synatax, markup
+@cindex syntax, markup
The markup syntax is similar to LilyPond's usual syntax: a
-@code{\markup} expression is enclosed in curly braces @code{@{
-@dots{} @}}. A single word is regarded as a minimal expression,
+@code{\markup} expression is enclosed in curly braces
+@code{@{@dots{} @}}. A single word is regarded as a minimal expression,
and therefore does not need to be enclosed with braces.
Unlike simple @qq{quoted text} indications, @code{\markup} blocks may
A @code{\markup} block may also contain quoted text strings. Such
strings are treated as minimal text expressions, and therefore any
-markup command or special character (such as @code{\} and @code{#})
+markup command or special character (such as @code{\} and@tie{}@code{#})
will be printed verbatim without affecting the formatting of the text.
Double quotation marks themselves may be printed by preceding them
with backslashes.
An exhaustive list of @code{\markup}-specific commands can be found in
@ref{Text markup commands}.
-
@seealso
Notation Reference:
@ref{Text markup commands}.
Snippets:
@rlsr{Text}.
-Installed files:
-@file{scm/@/markup@/.scm}.
-
+Installed Files:
+@file{scm/markup.scm}.
@knownissues
-
Syntax errors for markup mode can be confusing.
@cindex font size
@cindex text size
+@funindex \abs-fontsize
@funindex \fontsize
@funindex fontsize
@funindex \smaller
@funindex \magnify
@funindex magnify
-The size of the characters can also be altered in different ways:
-@itemize
-@item
-the font size can be set to predefined standard sizes,
+The font size can be altered, relative to the global staff size, in a
+number of different ways
-@item
-the font size can be set to an absolute value,
+It can be set to predefined size,
-@item
-the font size can also be changed relatively to its previous value.
-@end itemize
+@lilypond[quote,verbatim,relative=2]
+b1_\markup { \huge Sinfonia }
+b1^\markup { \teeny da }
+b1-\markup { \normalsize camera }
+@end lilypond
-@noindent
-The following example demonstrates these three methods:
+It can be set relative to its previous value,
-@lilypond[quote,verbatim,relative=1]
-f1_\markup {
- \tiny espressivo
- \large e
- \normalsize intenso
-}
-a^\markup {
- \fontsize #5 Sinfonia
- \fontsize #2 da
- \fontsize #3 camera
-}
-bes^\markup { (con
- \larger grande
- \smaller emozione
- \magnify #0.6 { e sentimento } )
-}
-d c2 r8 c bes a g1
+@lilypond[quote,verbatim,relative=2]
+b1_\markup { \larger Sinfonia }
+b1^\markup { \smaller da }
+b1-\markup { \magnify #0.6 camera }
+@end lilypond
+
+It can be increased or decreased relative to the value set by the
+global staff size,
+
+@lilypond[quote,verbatim,relative=2]
+b1_\markup { \fontsize #-2 Sinfonia }
+b1^\markup { \fontsize #1 da }
+b1-\markup { \fontsize #3 camera }
+@end lilypond
+
+It can also be set to a fixed point-size, regardless of the global staff
+size,
+
+@lilypond[quote,verbatim,relative=2]
+b1_\markup { \abs-fontsize #20 Sinfonia }
+b1^\markup { \abs-fontsize #8 da }
+b1-\markup { \abs-fontsize #14 camera }
@end lilypond
@cindex subscript
@funindex super
@funindex \sub
@funindex sub
+@funindex \normal-size-super
+@funindex normal-size-super
Text may be printed as subscript or superscript. By default these are
printed in a smaller size, but a normal size can be used as well:
@noindent
Some of these font families, used for specific items such as numbers
-or dynamics, do not provide all characters, as mentioned in @ref{New
-dynamic marks} and @ref{Manual repeat marks}.
+or dynamics, do not provide all characters, as mentioned in
+@ref{New dynamic marks} and @ref{Manual repeat marks}.
@c \concat is actually documented in Align (it is not
-@c a font-switching command). But we need it here. -vv
+@c a font-switching command). But we need it here. -vv
When used inside a word, some font-switching or formatting commands
may produce an unwanted blank space. This can easily be solved by
@code{\larger}.
@endpredefined
-
@seealso
Notation Reference:
@ref{Font},
@ref{Manual repeat marks},
@ref{Fonts}.
+Installed Files:
+@file{scm/define-markup-commands.scm}.
+
Snippets:
@rlsr{Text}.
Internals Reference:
@rinternals{TextScript}.
-Installed files:
-@file{scm/@/define@/-markup@/-commands@/.scm}.
+@knownissues
+Using the font sizing commands @code{\teeny}, @code{\tiny},
+@code{\small}, @code{\normalsize}, @code{\large}, and
+@code{\huge} will lead to inconsistent line spacing compared to
+using @code{\fontsize}.
@node Text alignment
@noindent
Some objects may have alignment procedures of their own, and therefore
are not affected by these commands. It is possible to move such
-markup objects as a whole, as shown for instance in @ref{Text marks}.
+markup objects as a whole, as shown for instance in
+@ref{Text marks}.
@cindex text, vertical alignment
@cindex vertical text alignment
\line \bold { Acto I }
\wordwrap \italic {
(La escena representa el corral de una casa de
- gitanos en el Albaicín de Granada. Al fondo una
+ gitanos en el Albaicín de Granada. Al fondo una
puerta por la que se ve el negro interior de
una Fragua, iluminado por los rojos resplandores
del fuego.)
\line \bold { Acto II }
\override #'(line-width . 50)
\justify \italic {
- (Calle de Granada. Fachada de la casa de Carmela
+ (Calle de Granada. Fachada de la casa de Carmela
y su hermano Manuel con grandes ventanas abiertas
a través de las que se ve el patio
donde se celebra una alegre fiesta)
An exhaustive list of text alignment commands can be found in
@ref{Align}.
-
@seealso
Learning Manual:
@rlearning{Moving objects}.
@ref{Align},
@ref{Text marks}.
+Installed Files:
+@file{scm/define-markup-commands.scm}.
+
Snippets:
@rlsr{Text}.
Internals Reference:
@rinternals{TextScript}.
-Installed files:
-@file{scm/@/define@/-markup@/-commands@/.scm}.
-
@node Graphic notation inside markup
@unnumberedsubsubsec Graphic notation inside markup
image files converted to the Encapsulated PostScript format
(@emph{eps}), or to directly embed graphics into the input file, using
native PostScript code. In such a case, it may be useful to
-explicitely specify the size of the drawing, as demonstrated below:
+explicitly specify the size of the drawing, as demonstrated below:
@lilypond[quote,verbatim,relative=1]
c1^\markup {
An exhaustive list of graphics-specific commands can be found in
@ref{Graphic}.
-
@seealso
Notation Reference:
@ref{Graphic},
-@ref{Editorial annotations}.
+@ref{Editorial annotations},
+@ref{Align}.
+
+Installed Files:
+@file{scm/define-markup-commands.scm},
+@file{scm/stencil.scm}.
Snippets:
@rlsr{Text}.
Internals Reference:
@rinternals{TextScript}.
-Installed files:
-@file{scm/@/define@/-markup@/-commands@/.scm},
-@file{scm/@/stencil@/.scm}.
-
@node Music notation inside markup
@unnumberedsubsubsec Music notation inside markup
More generally, any available musical symbol may be included
separately in a markup object, as demonstrated below; an exhaustive
-list of these symbols and their names can be found in @ref{The Feta
-font}.
+list of these symbols and their names can be found in
+@ref{The Feta font}.
@lilypond[quote,verbatim,relative=2]
c2
c2^\markup { \musicglyph #"timesig.neomensural94" }
@end lilypond
-Another way of printing non-text glyphs is described in @ref{Fonts
-explained}. This is useful for printing braces of various sizes.
+Another way of printing non-text glyphs is described in
+@ref{Fonts explained}. This is useful for printing braces of various
+sizes.
The markup mode also supports diagrams for specific
instruments:
c
c^\markup {
\combine
- \musicglyph #"accordion.accDiscant"
+ \musicglyph #"accordion.discant"
\combine
- \raise #0.5 \musicglyph #"accordion.accDot"
- \raise #1.5 \musicglyph #"accordion.accDot"
+ \raise #0.5 \musicglyph #"accordion.dot"
+ \raise #1.5 \musicglyph #"accordion.dot"
}
@end lilypond
An exhaustive list of music notation related commands can be found in
@ref{Music}.
-
@seealso
Notation Reference:
@ref{Music},
@ref{The Feta font},
@ref{Fonts explained}.
+Installed Files:
+@file{scm/define-markup-commands.scm},
+@file{scm/fret-diagrams.scm},
+@file{scm/harp-pedals.scm}.
+
Snippets:
@rlsr{Text}.
Internals Reference:
@rinternals{TextScript}.
-Installed files:
-@file{scm/@/define@/-markup@/-commands@/.scm},
-@file{scm/@/fret@/-diagrams@/.scm},
-@file{scm/@/harp@/-pedals@/.scm}.
-
@node Multi-page markup
@unnumberedsubsubsec Multi-page markup
@cindex markup text, multi-page
@cindex text spread over multiple pages
-@funindex \markuplines
-@funindex markuplines
+@funindex \markuplist
+@funindex markuplist
@funindex \justified-lines
@funindex justified-lines
@funindex \wordwrap-lines
pages:
@lilypond[quote,verbatim]
-\markuplines {
+\markuplist {
\justified-lines {
A very long text of justified lines.
...
An exhaustive list of markup list commands can be found in
@ref{Text markup list commands}.
-
@seealso
Notation Reference:
-@ref{Text markup list commands},
-@ref{New markup list command definition}.
+@ref{Text markup list commands}.
+
+Extending LilyPond:
+@rextend{New markup list command definition}.
+
+Installed Files:
+@file{scm/define-markup-commands.scm}.
Snippets:
@rlsr{Text}.
Internals Reference:
@rinternals{TextScript}.
-Installed files:
-@file{scm/@/define@/-markup@/-commands@/.scm}.
-
-
-@funindex \markuplines
-@funindex markuplines
+@funindex \markuplist
+@funindex markuplist
@predefined
-@code{\markuplines}.
+@code{\markuplist}.
@endpredefined
\vcenter {
\override #'(font-encoding . fetaBraces)
\lookup #"brace120"
- \override #'(font-encoding . fetaNumber)
- \column { 1 3 }
- \override #'(font-encoding . fetaDynamic)
- sf
+ \override #'(font-encoding . fetaText)
+ \column { 1 3 sf }
\override #'(font-encoding . fetaMusic)
\lookup #"noteheads.s0petrucci"
}
@ref{Rotating objects}.
Three families of text fonts are made available: the @emph{roman}
-(serif) font, that defaults to New Century Schoolbook, the @emph{sans}
-font and the monospaced @emph{typewriter} font -- these last two
-families are determined by the Pango installation.
+(serif) font, that defaults to New Century Schoolbook, the
+@emph{sans} font and the monospaced @emph{typewriter} font -- these
+last two families are determined by the Pango installation.
Each family may include different shapes and series. The following
example demonstrates the ability to select alternate families, shapes,
required change from the default size.
@lilypond[quote,verbatim,relative=2]
-\override Score.RehearsalMark #'font-family = #'typewriter
+\override Score.RehearsalMark.font-family = #'typewriter
\mark \markup "Ouverture"
-\override Voice.TextScript #'font-shape = #'italic
-\override Voice.TextScript #'font-series = #'bold
+\override Voice.TextScript.font-shape = #'italic
+\override Voice.TextScript.font-series = #'bold
d2.^\markup "Allegro"
-\override Voice.TextScript #'font-size = #-3
+\override Voice.TextScript.font-size = #-3
c4^smaller
@end lilypond
@noindent
A similar syntax may be used in markup mode; however in this case it
-is preferable to use the simpler syntax explained in @ref{Selecting
-font and font size}:
+is preferable to use the simpler syntax explained in
+@ref{Selecting font and font size}:
@lilypond[quote,verbatim]
\markup {
possible to use other fonts, as explained in the following sections:
@ref{Single entry fonts} and @ref{Entire document fonts}.
-
@seealso
Notation Reference:
@ref{The Feta font},
@ref{Music notation inside markup},
+@ref{Rotating objects},
@ref{Selecting font and font size},
@ref{Font}.
FontConfig may be used in a score, using the following syntax:
@lilypond[quote,verbatim,relative=2]
-\override Staff.TimeSignature #'font-name = #"Bitstream Charter"
-\override Staff.TimeSignature #'font-size = #2
+\override Staff.TimeSignature.font-name = #"Bitstream Charter"
+\override Staff.TimeSignature.font-size = #2
\time 3/4
a1_\markup {
lilypond -dshow-available-fonts x
@end example
-
@seealso
Notation Reference:
@ref{Fonts explained},
@rlsr{Text}.
@c A source file gets never installed...
-@c Installed files:
-@c @file{lily/@/font@/-config@/-scheme@/.cc}.
+@c Installed Files:
+@c @file{lily/font-config-scheme.cc}.
@node Entire document fonts
It is possible to change the fonts to be used as the default fonts in
the @emph{roman}, @emph{sans} and @emph{typewriter} font families by
-specifying them, in that order, as shown in the example below. For an
-explanation of fonts, see @ref{Fonts explained}.
+specifying them, in that order, as shown in the example below, which
+automatically scales the fonts with the value set for the global staff
+size. For an explanation of fonts, see @ref{Fonts explained}.
@cindex font families, setting
@cindex fonts, changing for entire document
@lilypond[verbatim,quote]
\paper {
- myStaffSize = #20
#(define fonts
(make-pango-font-tree "Times New Roman"
"Nimbus Sans"
"Luxi Mono"
- (/ myStaffSize 20)))
+ (/ (* staff-height pt) 2)))
}
\relative c'{
@c we don't do Helvetica / Courier, since GS incorrectly loads
@c Apple TTF fonts
-
@seealso
Notation Reference:
@ref{Fonts explained},
projects / lilypond.git / blobdiff