version that you are working on. See TRANSLATION for details.
@end ignore
-@c \version "2.11.61"
+@c \version "2.11.65"
@node Text
@section Text
* Fonts::
@end menu
+@node Writing text
+@subsection Writing text
+
+This section introduces different ways of adding text to a score.
+
@cindex Text, other languages
@warning{To write accented and special text (such as characters
from other languages), simply insert the characters directly into
the LilyPond file. The file must be saved as UTF-8. For more
information, see @ref{Text encoding}.}
-@node Writing text
-@subsection Writing text
-
-This section introduces different ways of adding text to a score.
-
@menu
* Text scripts::
* Text spanners::
syntax described in @ref{Direction and
placement}.
-@lilypond[quote,fragment,ragged-right,verbatim,relative=1]
-d8^"pizz." e f g a4-"scherz." f
+@lilypond[quote,verbatim,relative=2]
+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}.
-@lilypond[quote,fragment,ragged-right,verbatim,relative=1]
-d8^\markup { \italic pizz. } e f g
+@lilypond[quote,verbatim,relative=2]
+a8^\markup { \italic pizz. } g f e
a4_\markup { \tiny scherz. \bold molto } f
@end lilypond
in the following example, the first text string does not affect
spacing, whereas the second one does.
-@lilypond[quote,fragment,ragged-right,verbatim,relative=1]
-d8^"pizz." e f g
+@lilypond[quote,verbatim,relative=2]
+a8^"pizz." g f e
\textLengthOn
a4_"scherzando" f
@end lilypond
-@predefined
+@predefined
@funindex \textLengthOn
@code{\textLengthOn},
@funindex \textLengthOff
-@code{\textLengthOff}
+@code{\textLengthOff}.
+@endpredefined
@seealso
-
Notation Reference:
@ref{Formatting text},
@ref{Direction and placement}.
Internals Reference:
@rinternals{TextScript}.
+
@knownissues
Checking to make sure that text scripts and lyrics are within the
Such objects, called @qq{spanners}, may be created
from one note to another using the following syntax:
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
-\override TextSpanner #'bound-details #'left #'text = "rit."
+@lilypond[verbatim,quote,relative=2]
+\override TextSpanner #'(bound-details left text) = "rit."
b1\startTextSpan
e,\stopTextSpan
@end lilypond
but different formatting can be obtained using
@code{\markup} blocks, as described in @ref{Formatting text}.
-@lilypond[quote,ragged-right,fragment,relative=2,verbatim]
-\override TextSpanner #'bound-details #'left #'text =
+@lilypond[quote,relative=2,verbatim]
+\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}.
-@predefined
+@predefined
@funindex textSpannerUp
@code{\textSpannerUp},
@funindex textSpannerDown
@code{\textSpannerDown},
@funindex textSpannerNeutral
-@code{\textSpannerNeutral}
+@code{\textSpannerNeutral}.
+@endpredefined
-@seealso
+@seealso
Notation Reference:
@ref{Line styles},
@ref{Dynamics}.
@c \mark needs to be placed on a separate line (it's not
@c attached to an object like \markup is). -vv
-@lilypond[verbatim,quote,ragged-right,fragment,relative=2]
+@lilypond[verbatim,quote,relative=2]
c4
\mark "Allegro"
c c c
more complex text formatting may be added using a @code{\markup}
block, as described in @ref{Formatting text}:
-@lilypond[fragment,quote,ragged-right,verbatim,relative=1]
+@lilypond[quote,verbatim,relative=1]
<c e>1
\mark \markup { \italic { colla parte } }
<d f>2 <e g>
or fermata, by specifying the appropriate symbol name as explained in
@ref{Music notation inside markup}:
-@lilypond[fragment,quote,ragged-right,verbatim,relative=1]
-<f bes>2 <d aes'>
+@lilypond[quote,verbatim,relative=2]
+<bes f>2 <aes d>
\mark \markup { \musicglyph #"scripts.ufermata" }
<e g>1
@end lilypond
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[fragment,quote,ragged-right,verbatim,relative=2]
+@lilypond[quote,verbatim,relative=2]
\mark "Allegro"
c1 c
\mark "assai" \break
@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
{printing-marks-on-every-staff.ly}
-@seealso
+@seealso
Notation Reference:
@ref{Rehearsal marks},
@ref{Formatting text},
Internals Reference:
@rinternals{RehearsalMark}.
+
@knownissues
@c To be removed when Issue 69 in the tracker gets fixed. -vv
several music pieces, as described in
@ref{Multiple scores in a book}.
-@lilypond[quote,ragged-right,verbatim]
+@lilypond[quote,verbatim]
\score {
c'1
}
within LilyPond. This feature, and the specific syntax it
requires, are described in @ref{Multi-page markup}.
-@predefined
-@code{\markup},
+@predefined
@funindex \markuplines
-@code{\markuplines}
+@code{\markup},
+@code{\markuplines}.
+@endpredefined
+
-@ignore
@snippets
-TODO: add convenient snippets in input/new -vv
-@end ignore
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{stand-alone-two-column-markup.ly}
@seealso
-
Notation Reference: @ref{Formatting text},
@ref{File structure},
@ref{Multiple scores in a book},
entered using the backslash @code{\} character.
Such commands only affect the first following expression.
-@lilypond[quote,verbatim,fragment,relative=1]
-e1-\markup intenso
+@lilypond[quote,verbatim,relative=2]
+a1-\markup intenso
a2^\markup { poco \italic più forte }
c e1
d2_\markup { \italic "string. assai" }
the formatting of the text. Double quotation marks themselves
may be printed by preceding them with backslashes.
-@lilypond[quote,verbatim,fragment,relative=1]
-d1^"\italic markup..."
-d_\markup { \italic "... prints \"italic\" letters!" }
-d d
+@lilypond[quote,verbatim,relative=2]
+a1^"\italic markup..."
+a_\markup { \italic "... prints \"italic\" letters!" }
+a a
@end lilypond
To be treated as a distinct expression, a list of words needs
following example, the second @code{\markup} expression is
treated the same as the first one:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=2]
c1^\markup { \center-column { a bbb c } }
c1^\markup { \center-column { a { bbb c } } }
c1^\markup { \center-column { a \line { bbb c } } }
@seealso
-
Notation Reference:
@ref{Text markup commands}.
Defining custom font sets is also possible, as explained in
@ref{Fonts}.
-@predefined
+@predefined
@funindex \teeny
-@funindex \tiny
-@funindex \small
-@funindex \normalsize
-@funindex \large
-@funindex \huge
-@funindex \smaller
-@funindex \larger
@code{\teeny},
+@funindex \tiny
@code{\tiny},
+@funindex \small
@code{\small},
+@funindex \normalsize
@code{\normalsize},
+@funindex \large
@code{\large},
+@funindex \huge
@code{\huge},
+@funindex \smaller
@code{\smaller},
+@funindex \larger
@code{\larger}.
+@endpredefined
+
@seealso
Notation Reference:
example, there is no difference
between the first and the second markup.
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=2]
d1-\markup { poco }
f
d-\markup { \left-align poco }
Horizontal alignment may be fine-tuned
using a numeric value:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=2]
a1-\markup { \halign #-1 poco }
e'
a,-\markup { \halign #0 poco }
two possibilities; the last markup in this example has no anchor
point, and therefore is not moved.
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=1]
d2^\markup {
Acte I
\raise #2 { Scène 1 }
affected by these commands must be preceded with an
anchor point:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=1]
d2^\markup {
Acte I
\translate #'(-1 . 2) "Scène 1"
An exhaustive list of text alignment commands
can be found in @ref{Align}.
+
@seealso
Learning Manual:
@rlearning{Moving objects}.
may be useful to explicitely specify the size of the
drawing, as demonstrated below:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=1]
c1^\markup {
\combine
\epsfile #X #10 #"./context-example.eps"
An exhaustive list of graphics-specific commands
can be found in @ref{Graphic}.
+
@seealso
Notation Reference:
@ref{Graphic},
@file{scm/@/define@/-markup@/-commands@/.scm},
@file{scm/@/stencil@/.scm}.
+
@node Music notation inside markup
@unnumberedsubsubsec Music notation inside markup
Notes and accidentals can be entered using markup
commands:
-@lilypond[quote,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
a2 a^\markup {
\note #"4" #1
=
Other notation objects may also be printed
in markup mode:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=1]
g1 bes
ees-\markup {
\finger 4
below; an exhaustive list of these symbols and their
names can be found in @ref{The Feta font}.
-@lilypond[quote,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
c2
c'^\markup { \musicglyph #"eight" }
c,4
c16
c2^\markup { \musicglyph #"timesig.neomensural94" }
@end lilypond
+
@c TODO: add \lookup here? -vv
+@c Probably better not to document \lookup, which is useful only for
+@c printing braces, and instead document \left-brace and \right-brace
+@c when these become available -td
@noindent
Another way of printing non-text glyphs is described
The markup mode also supports diagrams for specific
instruments:
-@lilypond[quote,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
c1^\markup {
\fret-diagram-terse #"x;x;o;2;3;2;"
}
In such a case, the nested @code{\score} block must
contain a @code{\layout} block, as demonstrated here:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=1]
c4 d^\markup {
\score {
- \relative { c4 d e f }
+ \relative c' { c4 d e f }
\layout { }
}
}
An exhaustive list of music notation related commands can be
found in @ref{Music}.
+
@seealso
Notation Reference:
@ref{Music},
@file{scm/@/fret@/-diagrams@/.scm},
@file{scm/@/harp@/-pedals@/.scm}.
+
@node Multi-page markup
@unnumberedsubsubsec Multi-page markup
...
}
\wordwrap-lines {
- An other very long paragraph.
+ Another very long paragraph.
...
}
...
An exhaustive list of markup list commands can be found in
@ref{Text markup list commands}.
+
@seealso
Notation Reference:
@ref{Text markup list commands},
Installed files:
@file{scm/@/define@/-markup@/-commands@/.scm}.
+
@predefined
@funindex \markuplines
-@code{\markuplines}
+@code{\markuplines}.
+@endpredefined
@node Fonts
Music notation fonts can be described as a set of
specific glyphs, ordered in several families.
-The following syntax allows to directly use various
-LilyPond @code{feta} non-text fonts in markup mode:
+The following syntax allows various LilyPond @code{feta} non-text
+fonts to be used directly in markup mode:
-@lilypond[quote,verbatim,fragment,relative=2]
+@lilypond[quote,verbatim,relative=2]
a1^\markup {
\vcenter {
\override #'(font-encoding . fetaBraces)
Each family may include different shapes and series.
The following example demonstrates the ability to select
-alternate families, shapes, series and sizes:
-
-@lilypond[quote,verbatim,fragment,relative=2]
- \override Score.RehearsalMark #'font-family = #'typewriter
- \mark \markup "Ouverture"
- \key d \major
- \override Voice.TextScript #'font-shape = #'italic
- \override Voice.TextScript #'font-series = #'bold
- d'2.^\markup "Allegro"
- r4
+alternate families, shapes, series and sizes. The value
+supplied to @code{font-size} is the required change from the
+default size.
+
+@lilypond[quote,verbatim,relative=2]
+\override Score.RehearsalMark #'font-family = #'typewriter
+\mark \markup "Ouverture"
+\override Voice.TextScript #'font-shape = #'italic
+\override Voice.TextScript #'font-series = #'bold
+d2.^\markup "Allegro"
+\override Voice.TextScript #'font-size = #-3
+c4^smaller
@end lilypond
@noindent
}
@end lilypond
-@ignore
-@c FIXME: This needs an example -vv
-
-The size of the font may be set with the @code{font-size}
-property. The resulting size is taken relative to the
-@code{text-font-size} as defined in the @code{\paper} block.
-@end ignore
-
Although it is easy to switch between preconfigured fonts,
it is also 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{Selecting font and font size},
@ref{Font}.
+
@node Single entry fonts
@unnumberedsubsubsec Single entry fonts
Any font that is installed on the operating system and recognized
by FontConfig may be used in a score, using the following syntax:
-@lilypond[quote,verbatim,fragment,relative=1]
+@lilypond[quote,verbatim,relative=2]
\override Staff.TimeSignature #'font-name = #"Charter"
\override Staff.TimeSignature #'font-size = #2
\time 3/4
-c1_\markup {
+a1_\markup {
\override #'(font-name . "Vera Bold")
{ Vera Bold }
}
The last argument of the command can be anything, but has to be
present.
+
@seealso
Notation Reference:
@ref{Fonts explained},
Installed files:
@file{lily/@/font@/-config@/-scheme@/.cc}.
+
@node Entire document fonts
@unnumberedsubsubsec Entire document fonts
-
-It is possible to change the default font families for the
-entire document. In such a case, the following syntax has
-to be used, by providing three font families that will be
-respectively used as @emph{roman}, @emph{sans} and @emph{typewriter}
-fonts, as explained in @ref{Fonts explained}.
+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}.
@cindex font families, setting
@funindex make-pango-font-tree
@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