Guide, node Updating translation committishes..
@end ignore
-@c \version "2.13.36"
+@c \version "2.15.17"
@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
Notation Reference:
@ref{Formatting text},
-@ref{Direction and placement}.
+@ref{Direction and placement},
+@ref{Articulations and ornamentations}.
Snippets:
@rlsr{Text}.
@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
@snippets
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@lilypondfile[verbatim,quote,texidoc,doctitle]
{dynamics-text-spanner-postfix.ly}
-@lilypondfile[verbatim,lilyquote,texidoc,doctitle]
+@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},
@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]
+@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}
@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}
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.
@knownissues
-
Syntax errors for markup mode can be confusing.
@seealso
Notation Reference:
@ref{Graphic},
-@ref{Editorial annotations}.
+@ref{Editorial annotations},
+@ref{Align}.
Snippets:
@rlsr{Text}.
@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.
...
@file{scm/define-markup-commands.scm}.
-@funindex \markuplines
-@funindex markuplines
+@funindex \markuplist
+@funindex markuplist
@predefined
-@code{\markuplines}.
+@code{\markuplist}.
@endpredefined
Notation Reference:
@ref{The Feta font},
@ref{Music notation inside markup},
+@ref{Rotating objects},
@ref{Selecting font and font size},
@ref{Font}.