@refbugs
Dynamics are not centered, but workarounds do exist. See the
-``piano centered dynamics'' template in @ref{Piano templates}.
+@q{piano centered dynamics} template in @ref{Piano templates}.
@cindex cross staff stem
@cindex stem, cross staff
@cindex distance between staves in piano music
-The distance between the two staves is the same for all systems in the
-score. It is possible to override this per system, but it does require
-an arcane command incantation. See
-@inputfileref{input/@/test,piano@/-staff@/-distance@/.ly}.
-
@node Automatic staff changes
@subsection Automatic staff changes
b g \sustainUp a \sustainDown \bar "|."
@end lilypond
-The default `*Ped.' style for sustain and damper pedals corresponds to
+The default @q{*Ped.} style for sustain and damper pedals corresponds to
style @code{#'text}. The sostenuto pedal uses @code{mixed} style by
default.
@seealso
-In this manual: @ref{Laissez vibrer ties}
+In this manual: @ref{Laissez vibrer ties}.
@node Staff switch lines
@subsection Staff switch lines
staff, or vice versa.
@lilypond[ragged-right,verbatim,quote]
-stemExtend = \once \override Stem #'length = #22
+stemExtend = {
+ \once \override Stem #'length = #10
+ \once \override Stem #'cross-staff = ##t
+}
noFlag = \once \override Stem #'flag-style = #'no-flag
\new PianoStaff <<
\new Staff {
Other chords may be entered by suffixing a colon and introducing a
modifier (which may include a number if desired)
+
@lilypond[quote,fragment,verbatim]
\chordmode { e1:m e1:7 e1:m7 }
@end lilypond
-The first number following the root is taken to be the `type' of the
+
+The first number following the root is taken to be the @q{type} of the
chord, thirds are added to the root until it reaches the specified
-number
+number. The exception is @code{c:13}, for which the 11 is omitted.
+
@lilypond[quote,fragment,verbatim]
-\chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 }
+\chordmode { c:3 c:5 c:6 c:7 c:8 c:9 c:10 c:11 c:13}
@end lilypond
@cindex root of chord
More complex chords may also be constructed adding separate steps
to a chord. Additions are added after the number following
the colon and are separated by dots
+
@lilypond[quote,verbatim,fragment]
\chordmode { c:5.6 c:3.7.8 c:3.6.13 }
@end lilypond
+
Chord steps can be altered by suffixing a @code{-} or @code{+} sign
to the number
+
@lilypond[quote,verbatim,fragment]
\chordmode { c:7+ c:5+.3- c:3-.5-.7- }
@end lilypond
+
Removals are specified similarly and are introduced by a caret. They
must come after the additions
+
@lilypond[quote,verbatim,fragment]
\chordmode { c^3 c:7^5 c:9^3.5 }
@end lilypond
@funindex m
Since an unaltered 11 does not sound good when combined with an
-unaltered 3, the 11 is removed in this case (unless it is added
+unaltered 13, the 11 is removed in this case (unless it is added
explicitly)
@lilypond[quote,ragged-right,fragment,verbatim]
\chordmode { c:13 c:13.11 c:m13 }
@end lilypond
@funindex /+
-A bass note can be added instead transposed out of the chord,
+A bass note can be added instead of transposed out of the chord,
by using @code{/+}@var{pitch}.
@lilypond[quote,ragged-right,fragment,verbatim]
@lilypond[ragged-right,verbatim]
\new ChordNames \with {
\override BarLine #'bar-size = #4
- voltaOnThisStaff = ##t
\consists Bar_engraver
\consists "Volta_engraver"
}
@file{ly/@/chord@/-modifier@/-init@/.ly}.
For an example of tuning this property, see also
-@inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly}.
+@lsr{chords,chord@/-name@/-exceptions@/.ly}
@cindex exceptions, chord names.
This property contains the markup object used for the 7th step, when
it is major. Predefined options are @code{whiteTriangleMarkup} and
@code{blackTriangleMarkup}. See
-@inputfileref{input/@/regression,chord@/-name@/-major7@/.ly} for an example.
+@lsr{chords,chord@/-name@/-major7@/.ly} for an example.
@funindex chordNameSeparator
@item chordNameSeparator
@item chordRootNamer
The root of a chord is usually printed as a letter with an optional
alteration. The transformation from pitch to letter is done by this
-function. Special note names (for example, the German ``H'' for a
+function. Special note names (for example, the German @q{H} for a
B-chord) can be produced by storing a new function in this property.
@funindex chordNoteNamer
@funindex chordPrefixSpacer
@item chordPrefixSpacer
-The ``m'' for minor chords is usually printed right after the root of
+The @q{m} for minor chords is usually printed right after the root of
the chord. By setting @code{chordPrefixSpacer}, you can fix a spacer
-between the root and ``m''. The spacer is not used when the root
+between the root and @q{m}. The spacer is not used when the root
is altered.
@end table
There are also two other chord name schemes implemented: an alternate
Jazz chord notation, and a systematic scheme called Banter chords. The
alternate Jazz notation is also shown on the chart in @ref{Chord name
-chart}. Turning on these styles is described in the input file
-@inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
+chart}. Turning on these styles is demonstrated in
+@lsr{chords,chord-names-jazz.ly}.
@cindex Banter
@cindex jazz chords
@seealso
-Examples: @inputfileref{input/@/regression,chord@/-name@/-major7@/.ly},
-@inputfileref{input/@/regression,chord@/-name@/-exceptions@/.ly},
-@inputfileref{input/@/test,chord@/-names@/-jazz@/.ly}.
-
+Examples:
+@lsrdir{chords}
Init files: @file{scm/@/chords@/-ignatzek@/.scm}, and
@file{scm/@/chord@/-entry@/.scm}.
Song texts must be aligned with the notes of their melody.
@end itemize
-There are a few different ways to define lyrics; the simplest
-way is to use the @code{\addlyrics} function.
+There are a few different ways to define lyrics; we shall begin
+by examining the simplest method, and gradually increase complexity.
@menu
* Setting simple songs::
* Entering lyrics::
-* Hyphens and extenders::
-* The Lyrics context::
-* Melismata::
-* Another way of entering lyrics::
+* Aligning lyrics to a melody::
+* Working with lyrics and identifiers::
* Flexibility in placement::
* Spacing lyrics::
* More about stanzas::
@node Setting simple songs
@subsection Setting simple songs
-The easiest way to add lyrics to a melody is to append
@cindex \addlyrics
+
+The easiest way to add lyrics to a melody is to append
+
@example
\addlyrics @{ @var{the lyrics} @}
@end example
@end lilypond
The command @code{\addlyrics} cannot handle polyphony settings. For these
-cases you should use @code{\lyricsto} and @code{\lyricmode}.
+cases you should use @code{\lyricsto} and @code{\lyricmode}, as will be
+introduced in @ref{Entering lyrics}.
@cindex lyrics
@funindex \lyricmode
@cindex punctuation
+@cindex spaces, in lyrics
+@cindex quotes, in lyrics
-Lyrics are entered in a special input mode. This mode is introduced
+Lyrics are entered in a special input mode, which can be introduced
by the keyword @code{\lyricmode}, or by using @code{\addlyrics} or
@code{\lyricsto}. In this mode you can enter lyrics,
with punctuation and accents, and the input @code{d} is not parsed as
a pitch, but rather as a one letter syllable. Syllables are entered
like notes, but with pitches replaced by text. For example,
+
@example
\lyricmode @{ Twin-4 kle4 twin- kle litt- le star2 @}
@end example
of the syllables, either by specifying the duration of each syllable
explicitly, like in the example above, or by automatically aligning
the lyrics to a melody or other voice of music, using @code{\addlyrics}
-or @code{\lyricsto}. For more details see @ref{The Lyrics context}.
+or @code{\lyricsto}.
+@c TODO: broken
+@c For more details see @ref{The Lyrics context}.
A word or syllable of lyrics begins with an alphabetic character, and ends
with
any space or digit. The following characters can be any character
-that is not a digit or white space. One important consequence of this
-is that a word can end with @code{@}}. The following example is
-usually a mistake in the input file. The syllable includes a @code{@}}, so
-the
-opening brace is not balanced
+that is not a digit or white space.
+
+Any character that is not a digit or white space will be regarded as
+part of the syllable; one important consequence of this is that a word
+can end with @code{@}}, which often leads to the following mistake:
+
@example
-\lyricmode @{ twinkle@}
+\lyricmode @{ lah- lah@}
@end example
+In this example, the @code{@}} is included in the final syllable, so the
+opening brace is not balanced and the input file will probably not
+compile.
+
+
@funindex \property in \lyricmode
@noindent
Similarly, a period which follows an alphabetic sequence is included in
the resulting string. As a consequence, spaces must be inserted around
-property commands
+property commands: do @emph{not} write
+
+@example
+\override Score.LyricText #'font-shape = #'italic
+@end example
+
+@noindent
+but instead use
+
@example
\override Score . LyricText #'font-shape = #'italic
@end example
\relative { c2 e4 g2 e4 }
\addlyrics { gran- de_a- mi- go }
\addlyrics { pu- "ro y ho-" nes- to }
-\addlyrics { pu- ro~yho- nes- to }
+\addlyrics { pu- ro~y~ho- nes- to }
@end lilypond
The lyric ties is implemented with the Unicode character U+203F, so be
To enter lyrics with characters from non-English languages, or with
-non-ascii characters (such as the heart symbol or slanted quotes),
+accented and special characters (such as the heart symbol or slanted quotes),
simply insert the characters directly into the input file and save
-it with utf-8 encoding. See @ref{Text encoding} for more info.
+it with utf-8 encoding. See @ref{Text encoding}, for more info.
@lilypond[quote,ragged-right,fragment,verbatim]
\relative { e4 f e d e f e2 }
combination of a backslash followed by one of @code{`}, @code{'},
@code{"}, or @code{^}.
-To define indentifiers containing lyrics, the function @code{lyricmode}
+To define identifiers containing lyrics, the function @code{lyricmode}
must be used.
@example
-@node Hyphens and extenders
-@subsection Hyphens and extenders
-
-@cindex hyphens
-
-Centered hyphens are entered as `@code{--}' between syllables.
-The hyphen will have variable length depending on the space between
-the syllables and it will be centered between the syllables.
-
-@cindex melisma
-@cindex extender
-
-When a lyric is sung over many notes (this is called a melisma), this is
-indicated with a horizontal line centered between a syllable and the
-next one. Such a line is called an extender line, and it is entered as
-`@code{__}'.
-
-In tighly engraved music, hyphens can be removed. Whether this
-happens can be controlled with the @code{minimum-distance} (minimum
-distance between two syllables) and the @code{minimum-length}
-(threshold below which hyphens are removed).
-
-@seealso
-
-Program reference: @internalsref{LyricHyphen}, @internalsref{LyricExtender}.
-
+@node Aligning lyrics to a melody
+@subsection Aligning lyrics to a melody
+@funindex \lyricmode
+@funindex \addlyrics
+@funindex \lyricsto
-@node The Lyrics context
-@subsection The Lyrics context
Lyrics are printed by interpreting them in the context called
@internalsref{Lyrics}.
\new Lyrics \lyricmode @dots{}
@end example
+There are two main methods to specify the horizontal placement
+of the syllables:
+
+@itemize @bullet
+@item
+by automatically aligning
+the lyrics to a melody or other voice of music, using @code{\addlyrics}
+or @code{\lyricsto}.
+
+@item
+or by specifying the duration of each syllable
+explicitly, using @code{\lyricmode}
+@end itemize
+
+@menu
+* Automatic syllable durations::
+* Another way of entering lyrics::
+* Assigning more than one syllable to a single note::
+* More than one note on a single syllable::
+* Extenders and hyphens::
+@end menu
+
+@node Automatic syllable durations
+@subsubsection Automatic syllable durations
+
@cindex automatic syllable durations
-@funindex \lyricsto
@cindex lyrics and melodies
-This will place the lyrics according to the durations that were
-entered. The lyrics can also be aligned under a given melody
-automatically. In this case, it is no longer necessary to enter the
-correct duration for each syllable. This is achieved by combining the
+The lyrics can be aligned under a given melody
+automatically. This is achieved by combining the
melody and the lyrics with the @code{\lyricsto} expression
@example
\new Lyrics \lyricsto "blah" @{ LYRICS @}
@end example
-For different or more complex orderings, the best way is to setup the
-hierarchy of staves and lyrics first, e.g.,
+@node Another way of entering lyrics
+@subsubsection Another way of entering lyrics
+
+Lyrics can also be entered without @code{\addlyrics} or
+@code{\lyricsto}. In this case,
+syllables are entered like notes -- but with pitches replaced by text -- and the
+duration of each syllable must be entered explicitly. For example:
+
@example
-\new ChoirStaff <<
- \new Voice = "soprano" @{ @emph{music} @}
- \new Lyrics = "sopranoLyrics" @{ s1 @}
- \new Lyrics = "tenorLyrics" @{ s1 @}
- \new Voice = "tenor" @{ @emph{music} @}
->>
+play2 the4 game2.
+sink2 or4 swim2.
@end example
+
+The alignment to a melody can be specified with the
+@code{associatedVoice} property,
+
+ @example
+\set associatedVoice = #"lala"
+ @end example
+
+ @noindent
+The value of the property (here: @code{"lala"}) should be the name of
+a @internalsref{Voice} context. Without this setting, extender lines
+will not be formatted properly.
+
+Here is an example demonstrating manual lyric durations,
+
+@lilypond[relative=1,ragged-right,verbatim,fragment,quote]
+<< \new Voice = "melody" {
+ \time 3/4
+ c2 e4 g2.
+ }
+ \new Lyrics \lyricmode {
+ \set associatedVoice = #"melody"
+ play2 the4 game2.
+ } >>
+@end lilypond
-and then combine the appropriate melodies and lyric lines
+@seealso
+
+Program reference: @internalsref{Lyrics}.
-@example
-\context Lyrics = sopranoLyrics \lyricsto "soprano"
- @emph{the lyrics}
-@end example
-@noindent
-The final input would resemble
+@node Assigning more than one syllable to a single note
+@subsubsection Assigning more than one syllable to a single note
-@example
-<<\new ChoirStaff << @emph{setup the music} >>
- \lyricsto "soprano" @emph{etc}
- \lyricsto "alto" @emph{etc}
- @emph{etc}
->>
-@end example
+
+@funindex _
+@cindex ties, in lyrics
+
+In order to assign more than one syllable to a single note, you can
+surround them with quotes or use a @code{_} character, to get spaces
+between syllables, or use tilde symbol (@code{~}) to get a lyric
+tie@footnote{The lyric ties is implemented with the Unicode character
+U+203F, so be
+sure to have a font (Like DejaVuLGC) installed that includes this
+glyph.}.
+
+@lilypond[quote,relative=2,ragged-right,fragment,verbatim]
+\time 3/4
+\relative { c2 e4 g2 e4 }
+\addlyrics { gran- de_a- mi- go }
+\addlyrics { pu- "ro y ho-" nes- to }
+\addlyrics { pu- ro~y~ho- nes- to }
+@end lilypond
@seealso
-Program reference: @internalsref{LyricCombineMusic},
-@internalsref{Lyrics}.
+Program reference: @internalsref{LyricCombineMusic}.
+
+@c Here come the section which used to be "Melismata"
+@c the new title might be more self-explanatory
+
+
+@node More than one note on a single syllable
+@subsubsection More than one note on a single syllable
+
+@cindex melisma
+@cindex melismata
+@cindex phrasing, in lyrics
+
+Sometimes, particularly in Medieval music, several notes are to be sung on one
+single syllable; such vocalises are called melismas, or melismata.
+
+@c this method seems to be the simplest; therefore
+@c it might be better to present it first - vv
+
+You can define melismata entirely in the lyrics, by entering @code{_}
+for every note
+that is part of the melisma.
+@lilypond[relative=1,verbatim,fragment,quote]
+{ \set melismaBusyProperties = #'()
+ c d( e) f f( e) e e }
+\addlyrics
+ { Ky -- _ _ ri __ _ _ _ e }
+@end lilypond
-@node Melismata
-@subsection Melismata
+In this case, you can also have ties and slurs in the melody if you
+set @code{melismaBusyProperties}, as is done in the example above.
-The @code{\lyricsto} command detects melismata: it only puts one
+However, the @code{\lyricsto} command can also
+detect melismata automatically: it only puts one
syllable under a tied or slurred group of notes. If you want to force
an unslurred group of notes to be a melisma, insert @code{\melisma}
after the first note of the group, and @code{\melismaEnd} after the
beamed, and automatic beaming (see @ref{Setting automatic beam
behavior}) is switched off.
+@c TODO: there might be some more relevant place for
+@c the following link (?)
+
@cindex SATB
@cindex choral score
Program reference: @internalsref{Melisma_translator}.
-
-@inputfileref{input/@/regression,lyric@/-combine@/-new@/.ly}.
+@lsr{vocal,lyric@/-combine.ly}.
@refbugs
Melismata are not detected automatically, and extender lines must be
inserted by hand.
+@node Extenders and hyphens
+@subsubsection Extenders and hyphens
-@node Another way of entering lyrics
-@subsection Another way of entering lyrics
+@cindex melisma
+@cindex extender
-Lyrics can also be entered without @code{\lyricsto}. In this case the
-duration of each syllable must be entered explicitly, for example,
+Melismata are indicated with a horizontal line centered between a syllable
+and the next one. Such a line is called an extender line, and it is entered
+as @samp{ __ } (note the spaces before and after the two underscore
+characters).
-@example
-play2 the4 game2.
-sink2 or4 swim2.
-@end example
+@cindex hyphens
-The alignment to a melody can be specified with the
-@code{associatedVoice} property,
+Centered hyphens are entered as @samp{ -- } between syllables of a same word
+(note the spaces before and after the two hyphen characters). The hyphen
+will be centered between the syllables, and its length will be adjusted
+depending on the space between the syllables.
-@example
-\set associatedVoice = #"lala"
-@end example
+In tighly engraved music, hyphens can be removed. Whether this
+happens can be controlled with the @code{minimum-distance} (minimum
+distance between two syllables) and the @code{minimum-length}
+(threshold below which hyphens are removed).
-@noindent
-The value of the property (here: @code{"lala"}) should be the name of
-a @internalsref{Voice} context. Without this setting, extender lines
-will not be formatted properly.
+@seealso
-Here is an example demonstrating manual lyric durations,
+Program reference: @internalsref{LyricExtender},
+@internalsref{LyricHyphen}
-@lilypond[relative=1,ragged-right,verbatim,fragment,quote]
-<< \new Voice = "melody" {
- \time 3/4
- c2 e4 g2.
- }
- \new Lyrics \lyricmode {
- \set associatedVoice = #"melody"
- play2 the4 game2.
- } >>
-@end lilypond
+@node Working with lyrics and identifiers
+@subsection Working with lyrics and identifiers
+@cindex lyrics, identifiers
+To define identifiers containing lyrics, the function @code{\lyricmode}
+must be used. You do not have to enter durations though, if you add
+@code{\addlyrics} or @code{\lyricsto}
+when invoking your identifier.
+
+@example
+verseOne = \lyricmode @{ Joy to the world the Lord is come @}
+\score @{
+ <<
+ \new Voice = "one" \relative c'' @{
+ \autoBeamOff
+ \time 2/4
+ c4 b8. a16 g4. f8 e4 d c2
+ @}
+ \addlyrics @{ \verseOne @}
+ >>
+@}
+@end example
+
+@c TODO: Move the following section to
+@c "Working with lyrics and identifiers"
+
+For different or more complex orderings, the best way is to setup the
+hierarchy of staves and lyrics first, e.g.,
+@example
+\new ChoirStaff <<
+ \new Voice = "soprano" @{ @emph{music} @}
+ \new Lyrics = "sopranoLyrics" @{ s1 @}
+ \new Lyrics = "tenorLyrics" @{ s1 @}
+ \new Voice = "tenor" @{ @emph{music} @}
+>>
+@end example
+
+and then combine the appropriate melodies and lyric lines
+
+@example
+\context Lyrics = sopranoLyrics \lyricsto "soprano"
+@emph{the lyrics}
+@end example
+
+@noindent
+
+The final input would resemble
+
+@example
+<<\new ChoirStaff << @emph{setup the music} >>
+ \lyricsto "soprano" @emph{etc}
+ \lyricsto "alto" @emph{etc}
+@emph{etc}
+>>
+@end example
+
+@seealso
+
@c TODO: document \new Staff << Voice \lyricsto >> bug
+Program reference: @internalsref{LyricCombineMusic},
+@internalsref{Lyrics}.
@node Flexibility in placement
@subsection Flexibility in placement
* Lyrics to multiple notes of a melisma::
* Divisi lyrics::
* Switching the melody associated with a lyrics line::
-* Specifying melismata within the lyrics::
* Lyrics independent of notes::
@end menu
must be set one syllable @emph{before} the non-melismatic syllable
in the text, as shown here,
+@c FIXME: breaks compile
@lilypond[verbatim,ragged-right,quote]
+%{
<<
\relative \new Voice = "lahlah" {
\set Staff.autoBeaming = ##f
still
}
>>
+%}
@end lilypond
-The @code{ignoreMelismata} applies to the syllable ``fas'', so it
-should be entered before ``go''.
+The @code{ignoreMelismata} applies to the syllable @q{fas}, so it
+should be entered before @q{go}.
The reverse is also possible: making a lyric line slower than the
standard. This can be achieved by insert @code{\skip}s into the
@end lilypond
@noindent
-the text for the first stanza is set to a melody called ``lahlah'',
+the text for the first stanza is set to a melody called @q{lahlah},
@example
\new Lyrics \lyricsto "lahlah" @{
The second stanza initially is set to the @code{lahlah} context, but
-for the syllable ``ran'', it switches to a different melody.
+for the syllable @q{ran}, it switches to a different melody.
This is achieved with
@example
\set associatedVoice = alternative
Here, @code{alternative} is the name of the @code{Voice} context
containing the triplet.
-Again, the command must be one syllable too early, before ``Ty'' in
+Again, the command must be one syllable too early, before @q{Ty} in
this case.
@example
@code{lahlah} to @code{associatedVoice}.
-@node Specifying melismata within the lyrics
-@subsubsection Specifying melismata within the lyrics
-
-It is also possible to define melismata entirely in the lyrics. This
-can be done by entering @code{_} for every note that is part of the
-melisma.
-
-@lilypond[relative=1,verbatim,fragment,quote]
-{ \set melismaBusyProperties = #'()
- c d( e) f f( e) e e }
-\addlyrics
- { Ky -- _ _ ri __ _ _ _ e }
-@end lilypond
-
-In this case, you can also have ties and slurs in the melody if you
-set @code{melismaBusyProperties}, as is done in the example above.
-
-
@node Lyrics independent of notes
@subsubsection Lyrics independent of notes
@lilypond[relative,verbatim,quote,ragged-right]
\score {
- {
+ \relative c' {
c c c c
c c c c
}
@node More about stanzas
@subsection More about stanzas
-@cindex phrasing, in lyrics
-
-
@cindex stanza number
-@cindex singer's names
-@cindex name of singer
+@subsubsection Adding stanza numbers
Stanza numbers can be added by setting @code{stanza}, e.g.,
}
@end lilypond
-These numbers are put just before the start of first syllable.
+@noindent
+These numbers are put just before the start of the first syllable.
+
+
+@subsubsection Adding dynamics marks
+
+Stanzas differing in loudness may be indicated by putting a
+dynamics mark before each stanza. In Lilypond, everthing coming in
+front of a stanza goes into the @code{StanzaNumber} object; dynamics marks
+are no different. For technical reasons, you have to set the stanza
+outside @code{\lyricmode}:
+
+@lilypond[quote,ragged-right,verbatim]
+text = {
+ \set stanza = \markup { \dynamic "ff" "1. " }
+ \lyricmode {
+ Big bang
+ }
+}
+
+<<
+ \new Voice = "tune" {
+ \time 3/4
+ g'4 c'2
+ }
+\new Lyrics \lyricsto "tune" \text
+>>
+@end lilypond
+
+@cindex singer name
+@cindex name of singer
+@subsubsection Adding singer names
+
+Names of singers can also be added. They are printed at the start of
+the line, just like instrument names. They are created by setting
+@code{vocalName}. A short version may be entered as @code{shortVocalName}.
+
+@lilypond[fragment,ragged-right,quote,verbatim,relative=2]
+\new Voice {
+ \time 3/4 g2 e4 a2 f4 g2.
+} \addlyrics {
+ \set vocalName = "Bert "
+ Hi, my name is Bert.
+} \addlyrics {
+ \set vocalName = "Ernie "
+ Oh, che -- ri, je t'aime
+}
+@end lilypond
+
+
+@subsubsection Printing stanzas at the end
Sometimes it is appropriate to have one stanza set
to the music, and the rest added in verse form at
its fleece was white as snow.
}
-\book{
- \score{ <<
- \new Voice = "one" { \melody }
- \new Lyrics \lyricsto "one" \text
- >>
- \layout { }
- }
- \markup { \column{
- \line{ Verse 2. }
- \line{ All the children laughed and played }
- \line{ To see a lamb at school. }
- }
- }
- \markup{
- \wordwrap-string #"
- Verse 3.
-
- Mary took it home again,
-
- It was against the rule."
+\score{ <<
+ \new Voice = "one" { \melody }
+ \new Lyrics \lyricsto "one" \text
+>>
+ \layout { }
+}
+\markup { \column{
+ \line{ Verse 2. }
+ \line{ All the children laughed and played }
+ \line{ To see a lamb at school. }
}
}
-@end lilypond
+\markup{
+ \wordwrap-string #"
+ Verse 3.
+ Mary took it home again,
-Names of singers can also be added. They are printed at the start of
-the line, just like instrument names. They are created by setting
-@code{vocalName}. A short version may be entered as @code{shortVocalName}.
-
-
-@lilypond[fragment,ragged-right,quote,verbatim,relative=2]
-\new Voice {
- \time 3/4 g2 e4 a2 f4 g2.
-} \addlyrics {
- \set vocalName = "Bert "
- Hi, my name is Bert.
-} \addlyrics {
- \set vocalName = "Ernie "
- Oh, che -- ri, je t'aime
+ It was against the rule."
}
@end lilypond
+@subsubsection Printing stanzas at the end in multiple columns
+
When a piece of music has many verses, they are often printed in
multiple columns across the page. An outdented verse number often
introduces each verse. The following example shows how to produce such
@internalsref{AmbitusLine}, @internalsref{AmbitusNoteHead},
@internalsref{AmbitusAccidental}.
-Examples: @inputfileref{input/@/regression,ambitus@/.ly}.
+Examples:
+@lsr{vocal,ambitus@/.ly}.
@refbugs
examples, and that might get them more involved in the docs. -gp
@end ignore
-``Parlato'' is spoken without pitch but still with rhythm; it is
+@q{Parlato} is spoken without pitch but still with rhythm; it is
notated by cross noteheads. This is demonstrated in
@ref{Special noteheads}.
Program reference: @internalsref{RhythmicStaff}.
-Examples: @inputfileref{input/@/regression,rhythmic@/-staff@/.ly}.
-
@node Entering percussion
@subsection Entering percussion
<c\1 e\2 g\3>
@end lilypond
-See also @inputfileref{input/regression,string-number.ly}.
-
@seealso
-Program reference: @internalsref{StringNumber}.
+Program reference: @internalsref{StringNumber},
+@lsr{guitar/,string-number.ly}.
@node Tablatures basic
@seealso
-Examples: @inputfileref{input/@/test,fret@/-diagram@/.ly}
+Examples: @lsrdir{guitar}
@node Right hand fingerings
\clef "G_8"
b16 d16 g16 b16 e16
\textSpannerDown
-\override TextSpanner #'edge-text = #'("XII " . "")
+\override TextSpanner #'bound-details #'left #'text = #"XII "
g16\startTextSpan
b16 e16 g16 e16 b16 g16\stopTextSpan
e16 b16 g16 d16
@ref{Figured bass}
@end itemize
-Here are all suptopics at a glance:
+Here are all subtopics at a glance:
@menu
* Ancient note heads::
note head style. Still, the note head style can be set, e.g., to
@code{vaticana_punctum} to produce punctum neumes. Similarly, a
@internalsref{Mensural_ligature_engraver} is used to automatically
-assemble mensural ligatures. See @ref{Ligatures} for how ligature
+assemble mensural ligatures. See @ref{Ligatures}, for how ligature
engravers work.
@seealso
-Examples: @inputfileref{input/@/regression,note@/-head@/-style@/.ly} gives an
-overview over all available note head styles.
+@ref{Note head styles}, gives an overview over all available note head styles.
@node Ancient accidentals
As shown, not all accidentals are supported by each style. When
trying to access an unsupported accidental, LilyPond will switch to a
different style, as demonstrated in
-@inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
+@lsr{ancient,ancient-accidentals.ly}.
Similarly to local accidentals, the style of the key signature can be
controlled by the @code{glyph-name-alist} property of the
@seealso
-In this manual: @ref{Pitches}, @ref{Cautionary accidentals} and
-@ref{Automatic accidentals} give a general introduction of the use of
-accidentals. @ref{Key signature} gives a general introduction of
+In this manual: @ref{Pitches}, @ref{Cautionary accidentals}, and
+@ref{Automatic accidentals}, give a general introduction of the use of
+accidentals. @ref{Key signature}, gives a general introduction of
the use of key signatures.
Program reference: @internalsref{KeySignature}.
-Examples: @inputfileref{input/@/test,ancient@/-accidentals@/.ly}.
+Examples: @lsrdir{ancient}
@node Ancient rests
@subsection Ancient rests
There are no 32th and 64th rests specifically for the mensural or
neo-mensural style. Instead, the rests from the default style will be
-taken. See @inputfileref{input/@/test,rests@/.ly} for a chart of all
-rests.
+taken. See @lsr{pitches,rests} for a chart of all rests.
There are no rests in Gregorian Chant notation; instead, it uses
@ref{Divisiones}.
@seealso
-In this manual: @ref{Rests} gives a general introduction into the use of
+In this manual: @ref{Rests}, gives a general introduction into the use of
rests.
-@emph{Modern style} means ``as is typeset in contemporary editions of
-transcribed mensural music''.
+@emph{Modern style} means @qq{as is typeset in contemporary editions of
+transcribed mensural music.}
-@emph{Petrucci style} means ``inspired by printings published by the
-famous engraver Petrucci (1466-1539)''.
+@emph{Petrucci style} means @qq{inspired by printings published by the
+famous engraver Petrucci (1466-1539).}
-@emph{Historic style} means ``as was typeset or written in historic
-editions (other than those of Petrucci)''.
+@emph{Historic style} means @qq{as was typeset or written in historic
+editions (other than those of Petrucci).}
-@emph{Editio XXX style} means ``as is/was printed in Editio XXX''.
+@emph{Editio XXX style} means @qq{as is/was printed in Editio XXX.}
Petrucci used C clefs with differently balanced left-side vertical
beams, depending on which staff line it is printed.
@seealso
-This manual: @ref{Time signature} gives a general introduction to
+This manual: @ref{Time signature}, gives a general introduction to
the use of time signatures.
@refbugs
@refbugs
Some articulations are vertically placed too closely to the
-correpsonding note heads.
+corresponding note heads.
The episem line is not displayed in many cases. If it is displayed,
the right end of the episem line is often too far to the right.
@cindex custos
@cindex custodes
-A @emph{custos} (plural: @emph{custodes}; Latin word for `guard') is a
+A @emph{custos} (plural: @emph{custodes}; Latin word for @q{guard}) is a
symbol that appears at the end of a staff. It anticipates the pitch
of the first note(s) of the following line thus helping the performer
to manage line breaks during performance.
Program reference: @internalsref{Custos}.
-Examples: @inputfileref{input/@/regression,custos@/.ly}.
+Examples:
+@lsr{ancient,custodes@/.ly}.
@node Divisiones
@cindex finalis
A @emph{divisio} (plural: @emph{divisiones}; Latin word for
-`division') is a staff context symbol that is used to structure
+@q{division}) is a staff context symbol that is used to structure
Gregorian music into phrases and sections. The musical meaning of
@emph{divisio minima}, @emph{divisio maior}, and @emph{divisio maxima}
can be characterized as short, medium, and long pause, somewhat like
Program reference: @internalsref{BreathingSign}.
-Examples: @inputfileref{input/@/test,divisiones@/.ly}.
+Examples: @lsr{expressive,breathing-sign.ly}.
+
@node Ligatures
@subsection Ligatures
accordingly extrapolated. This way, infinitely many different
ligatures can be created.
-@c TODO: create a regression or tips & tricks example document with
-@c even more Gregorian ligatures, and add a link to this document
-@c here.
-
Augmentum dots, also called @emph{morae}, are added with the music
function @code{\augmentum}. Note that @code{\augmentum} is
implemented as a unary music function rather than as head prefix. It
In European music from before about 1600, singers were often expected
to chromatically alter notes at their own initiative. This is called
-``Musica Ficta''. In modern transcriptions, these accidentals are
+@q{Musica Ficta}. In modern transcriptions, these accidentals are
usually printed over the note.
@cindex Accidental, musica ficta
@end lilypond
+@commonprop
+
+By default, this method produces figures above the notes. To get
+figures below the notes, use
+
+@example
+\override Staff.BassFigureAlignmentPositioning #'direction = #DOWN
+@end example
+
+
@refbugs
When using figured bass above the staff with extender lines and
@code{implicitBassFigures} the lines may become swapped around.
Maintaining order consistently will be impossible when multiple figures
-have overlapping extender lines. To avoid this problem, plese
+have overlapping extender lines. To avoid this problem, please
use @code{stacking-dir} on @code{BassFigureAlignment}.
projects / lilypond.git / blobdiff