|
|
GNU LilyPondWelcome to the home of the GNU Music Typesetter |
||||||||||
|
Node:Text markup, Next:Invisible grobs, Previous:Font selection, Up:Tuning output Text markupLilyPond has an internal mechanism to typeset texts. You can
form text markup expressions by composing scheme expressions
in the following way.
\relative c' {
\fatText
a^#"upright"
b_#'(bold "bold")
c^#'(italic "italic")
d_#'((bold italic) "ff")
e^#'(dynamic "ff")
f_#'(lines "one" (bold "two"))
g^#'(music "noteheads-2" ((raise . 2.4) "flags-u3"))
}
Normally, the Scheme markup text is stored in the text: string | (head? text+) head: markup | (markup+) markup-item: property | abbrev property: (key . value) abbrev: The markup is broken down and converted into a list of grob properties, which are prepended to the property list. The key-value pair is a grob property. A list of properties available is included in the generated documentation for Text_interface . The following abbreviations are currently defined:
One practical application of complicated markup is to fake a metronome
marking:
#(define note '(columns
(music "noteheads-2" ((kern . -0.1) "flags-stem"))))
#(define eight-note `(columns ,note ((kern . -0.1)
(music ((raise . 3.5) "flags-u3")))))
#(define dotted-eight-note
`(columns ,eight-note (music "dots-dot")))
\score {
\notes\relative c'' {
a1^#`((columns (font-relative-size . -1)) ,dotted-eight-note " = 64")
}
\paper {
linewidth = -1.
\translator{
\ScoreContext
TextScript \override #'font-shape = #'upright
}
}
}
|
||||||||||
|
Go back to index of LilyPond.
Please send GNU LilyPond questions and comments to lilypond-user@gnu.org. Please send comments on these web pages to lilypond@packages.debian.org Copyright (c) 1997--2001 Han-Wen Nienhuys and Jan Nieuwenhuizen. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. |
|||||||||||
This page was built from LilyPond-1.4.12 (stable-branch) by