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"
@menu
* Common notation for vocal music::
-* Entering lyrics::
-* Aligning lyrics to a melody::
-* Specific uses of lyrics::
+* Techniques specific to lyrics::
* Stanzas::
+* Songs::
+* Choral::
+* Opera and stage musicals::
+* Chants psalms and hymns::
+* Ancient vocal music::
+
@end menu
@node Common notation for vocal music
@subsection Common notation for vocal music
-This section discusses issues related to vocal music in general, and
-to some particular styles of vocal music.
+This section discusses issues common to most types of vocal music.
@menu
-* References for vocal music and lyrics::
-* Opera::
-* Song books::
-* Spoken music::
-* Chants::
-* Ancient vocal music::
+* References for vocal music::
+* Entering lyrics::
+* Aligning lyrics to a melody::
+* Automatic syllable durations::
+* Manual syllable durations::
+* Multiple syllables to one note::
+* Multiple notes to one syllable::
+* Skipping notes::
+* Extenders and hyphens::
@end menu
-@node References for vocal music and lyrics
-@unnumberedsubsubsec References for vocal music and lyrics
+@node References for vocal music
+@unnumberedsubsubsec References for vocal music
-@c TODO: split this section in two parts? -vv
-
-Various issues may arise when engraving vocal music. Some of these
-are discussed in this section, while others are explained elsewhere:
+This section indicates where to find details of notation issues
+that may arise in any type of vocal music.
@itemize
+
@item
Most styles of vocal music use written text as lyrics. An introduction
to this notation is to be found in @rlearning{Setting simple songs}.
This syntax is described in @ref{Text markup introduction}.
@item
-Lead sheets may be printed by combining vocal parts and @q{chord mode};
-this syntax is explained in @ref{Chord notation}.
-
-@item
-@q{Ambitus} may be added at the beginning of vocal staves, as explained
+@notation{Ambitus} may be added at the beginning of vocal staves, as explained
in @ref{Ambitus}.
-@item
-Vocal parts may be printed using traditional clefs, as shown in @ref{Clef}.
-
-@item
-Ancient vocal music is supported, as explained in @ref{Ancient notation}.
@end itemize
-
-@node Opera
-@unnumberedsubsubsec Opera
-
-@c TODO
-TBC
-
-@c add characters names snippet -vv
-
-@node Song books
-@unnumberedsubsubsec Song books
-
-@c TODO
-TBC
-
-@snippets
-@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
-{simple-lead-sheet.ly}
-
-
-@seealso
-Notation Reference:
-@ref{Chord notation}.
-
-
-@node Spoken music
-@unnumberedsubsubsec Spoken music
-@cindex parlato
-@cindex Sprechgesang
-Such effects as @q{parlato} or @q{Sprechgesang} require perfomers to speak
-without pitch but still with rhythm; these are notated by cross
-note heads, as demonstrated in @ref{Special note heads}.
-
-@c TODO add "marking-notes-on-spoken-parts" snippet -vv
-@c add "showing the rhythm of a melody" snip
-@c add "one staff-line notation"
-@c add "improvisation" ref
-@c add "lyrics independents of notes" ref
-
-@node Chants
-@unnumberedsubsubsec Chants
-
-@c TODO Add text from lsr and -user
-TBC
-
-@node Ancient vocal music
-@unnumberedsubsubsec Ancient vocal music
-
-@c TODO
-TBC
-
-@c Add "Printing both the ancient and the modern clef in vocal music" snippet,
-@c and "Transcription of Ancient music with incipit" snippet. -vv
-
-
@seealso
-Notation Reference:
-@ref{Ancient notation}.
-
+Music Glossary:
+@rglos{ambitus}.
@node Entering lyrics
-@subsection Entering lyrics
+@unnumberedsubsubsec Entering lyrics
-@c TODO add one sentence here. -vv
-
-@menu
-* Lyrics explained::
-* Setting simple songs::
-* Working with lyrics and variables::
-@end menu
-
-
-@node Lyrics explained
-@unnumberedsubsubsec Lyrics explained
+Lyrics are entered in lyric mode. This section explains how this
+done.
@cindex lyrics
@funindex \lyricmode
@cindex spaces, in lyrics
@cindex quotes, in lyrics
-@c FIXME: this section is to be rewritten.
+@c TODO: this section is to be rewritten.
Since LilyPond input files are text, there is at least one
issue to consider when working with vocal music:
song texts must be interpreted as text, not notes. For example, the
@rinternals{LyricSpace}.
-@c FIXME: this title has to be changed (possible confusion with LM) -vv
-@node Setting simple songs
-@unnumberedsubsubsec Setting simple songs
-
-@cindex \addlyrics
-
-The easiest way to add lyrics to a melody is to append
-
-@example
-\addlyrics @{ @var{the lyrics} @}
-@end example
-
-@noindent
-to a melody. Here is an example,
-
-@lilypond[ragged-right,verbatim,fragment,quote]
-\time 3/4
-\relative c' { c2 e4 g2. }
-\addlyrics { play the game }
-@end lilypond
-
-More stanzas can be added by adding more
-@code{\addlyrics} sections
-
-@lilypond[ragged-right,verbatim,fragment,quote]
-\time 3/4
-\relative c' { c2 e4 g2. }
-\addlyrics { play the game }
-\addlyrics { speel het spel }
-\addlyrics { joue le jeu }
-@end lilypond
-
-The command @code{\addlyrics} cannot handle polyphony settings. For these
-cases you should use @code{\lyricsto} and @code{\lyricmode}, as will be
-introduced in @ref{Lyrics explained}.
-
-@c TODO: one additional section may be needed here,
-@c such as "advanced lyric syntax" or whatever -vv
-
-@node Working with lyrics and variables
-@unnumberedsubsubsec Working with lyrics and variables
-
-@cindex lyrics, variables
-
-To define variables 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 variable.
-
-@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
-
-For different or more complex orderings, the best way is to set up 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
-
-@noindent
-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
-
-@ignore
-@c FIXME
-http://code.google.com/p/lilypond/issues/detail?id=329
-The problem cannot be reproduced.
-The following has no sense, because the issue seems to be fixed.
-A comment is in tracker waiting for response ---FV
-
-
-Be careful when defining a variable with lyrics that creates a new
-context, for example, using the deprecated @code{\lyrics} command. See
-the next erroneous example:
-
-@example
-words = \lyrics{ %warning: this creates a new context
- one two
-}
-<<
- \new Voice = "sop" { c1 }
- \new Lyrics \lyricsto "sop" { \words }
- \new Voice = "alt" { c2 c }
- \new Lyrics \lyricsto "alt" { \words }
->>
-@end example
-
-the problem is that \lyricsto will try to connect the "sop" melody with the context
-created by "\new Lyrics".
-
-Then \lyrics in \words creates another context, and the original "\new Lyrics" one
-remains empty.
-
-@end ignore
-
-
-@seealso
-@c TODO: document \new Staff << Voice \lyricsto >> bug
-Internals Reference:
-@rinternals{LyricCombineMusic},
-@rinternals{Lyrics}.
-
-
@node Aligning lyrics to a melody
-@subsection Aligning lyrics to a melody
+@unnumberedsubsubsec Aligning lyrics to a melody
@funindex \lyricmode
@funindex \addlyrics
@funindex \lyricsto
-@c FIXME: this stuff is to be rewritten. -vv
+@c TODO: this stuff is to be rewritten. -vv
Aligning of text with melodies can be made automatically, but if you
specify the durations of the syllables it can also be made manually.
@ref{Keeping contexts alive}.
-@menu
-* Automatic syllable durations::
-* Manual syllable durations::
-* Multiple syllables to one note::
-* Multiple notes to one syllable::
-* Skipping notes::
-* Extenders and hyphens::
-* Lyrics and repeats::
-@end menu
-
@node Automatic syllable durations
@unnumberedsubsubsec Automatic syllable durations
-@cindex automatic syllable durations
+@cindex syllable durations, automatic
@cindex lyrics and melodies
The lyrics can be aligned under a given melody
The second stanza is not properly aligned because the durations
were not specified. A solution for that would be to use @code{\lyricsto}.
+@cindex \addlyrics
+
The @code{\addlyrics} command is actually just a convenient way
to write a more complicated LilyPond structure that sets up the
lyrics.
\new Lyrics \lyricsto "blah" @{ LYRICS @}
@end example
+Here is an example,
+
+@lilypond[ragged-right,verbatim,fragment,quote]
+\time 3/4
+\relative c' { c2 e4 g2. }
+\addlyrics { play the game }
+@end lilypond
+
+More stanzas can be added by adding more
+@code{\addlyrics} sections
+
+@lilypond[ragged-right,verbatim,fragment,quote]
+\time 3/4
+\relative c' { c2 e4 g2. }
+\addlyrics { play the game }
+\addlyrics { speel het spel }
+\addlyrics { joue le jeu }
+@end lilypond
+
+The command @code{\addlyrics} cannot handle polyphony settings.
+For these cases you should use @code{\lyricsto} and
+@code{\lyricmode}, for details see @ref{Entering lyrics}.
+
@node Manual syllable durations
@unnumberedsubsubsec Manual syllable durations
You can define melismata entirely in the lyrics, by entering @code{_}
for every extra note that has to be added to the melisma.
-@c FIXME: clarify: __ is used to crate a lyric extender,
+@c TODO: clarify: __ is used to crate a lyric extender,
@c _ is used to add a note to a melisma, so both __ and _ are needed.
@c verbose! --FV
@c duplicated: TODO fix
-Additionaly, you can make an extender line to be typeset to indicate
+Additionally, you can make an extender line to be typeset to indicate
the melisma in the score, writing a double underscore next to the
-first syllable of the melisma. This example shows the three elements
+first syllable of the melisma. This example shows the three elements
that are used for this purpose (all of them surrounded by spaces):
double hyphens to separate syllables in a word, underscores to add
notes to a melisma, and a double underscore to put an extender line.
-@c wrong: extender line only on last syllable of a word. Change example
+@c wrong: extender line only on last syllable of a word. Change example
@lilypond[relative=1,verbatim,fragment,quote]
{ \set melismaBusyProperties = #'()
c d( e) f f( e) e e }
beamed, and automatic beaming (see @ref{Setting automatic beam
behavior}) is switched off.
-@c FIXME: this now links to LM -vv
+@lilypond[quote,relative=2,ragged-right,fragment,verbatim]
+<<
+ \new Voice = "lala" {
+ \time 3/4
+ \autoBeamOff
+ f4 g8[ f e f]
+ e2
+ }
+ \new Lyrics \lyricsto "lala" {
+ la di __ daah
+ }
+>>
+@end lilypond
+
+@c TODO: this now links to LM -vv
+@c umm, yeah... so what? -gp
@cindex SATB
@cindex choral score
@rinternals{LyricHyphen}.
-@node Lyrics and repeats
-@unnumberedsubsubsec Lyrics and repeats
-
-@c TODO New section. Add text
-TBC
-
-
-@node Specific uses of lyrics
-@subsection Specific uses of lyrics
-
-@c FIXME This whole section is to be reorganized. -vv
+@node Techniques specific to lyrics
+@subsection Techniques specific to lyrics
-Often, different stanzas of one song are put to one melody in slightly
-differing ways. Such variations can still be captured with
-@code{\lyricsto}.
+@c TODO This whole section is to be reorganized. -vv
@menu
+* Working with lyrics and variables::
+* Lyrics and repeats::
* Divisi lyrics::
* Lyrics independent of notes::
* Spacing out syllables::
-* Centering lyrics between staves::
+* Placement of lyrics between staves::
@end menu
-@node Divisi lyrics
+@node Working with lyrics and variables
+@unnumberedsubsubsec Working with lyrics and variables
+
+@cindex lyrics, variables
+
+To define variables 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 variable.
+
+@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
+
+For different or more complex orderings, the best way is to set up 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
+
+@noindent
+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
+
+@ignore
+@c TODO
+http://code.google.com/p/lilypond/issues/detail?id=329
+The problem cannot be reproduced.
+The following has no sense, because the issue seems to be fixed.
+A comment is in tracker waiting for response ---FV
+
+
+Be careful when defining a variable with lyrics that creates a new
+context, for example, using the deprecated @code{\lyrics} command. See
+the next erroneous example:
+
+@example
+words = \lyrics{ %warning: this creates a new context
+ one two
+}
+<<
+ \new Voice = "sop" { c1 }
+ \new Lyrics \lyricsto "sop" { \words }
+ \new Voice = "alt" { c2 c }
+ \new Lyrics \lyricsto "alt" { \words }
+>>
+@end example
+
+the problem is that \lyricsto will try to connect the "sop" melody with the context
+created by "\new Lyrics".
+
+Then \lyrics in \words creates another context, and the original "\new Lyrics" one
+remains empty.
+
+@end ignore
+
+
+@seealso
+@c TODO: document \new Staff << Voice \lyricsto >> bug
+Internals Reference:
+@rinternals{LyricCombineMusic},
+@rinternals{Lyrics}.
+
+
+@node Lyrics and repeats
+@unnumberedsubsubsec Lyrics and repeats
+
+@c TODO New section. Add text
+TBC
+
+
+@node Divisi lyrics
@unnumberedsubsubsec Divisi lyrics
You can display alternate (or divisi) lyrics by naming voice
This method is recommended only if the music in the @code{Devnull}
context does not contain melismata. Melismata are defined by the
-@code{Voice} context. Connecting lyrics to a @code{Devnull} context
+@code{Voice} context. Connecting lyrics to a @code{Devnull} context
makes the voice/lyrics links to get lost, and so does the info on
melismata. Therefore, if you link lyrics to a @code{Devnull} context,
the implicit melismata get ignored.
@end ignore
-@node Centering lyrics between staves
-@unnumberedsubsubsec Centering lyrics between staves
+@node Placement of lyrics between staves
+@unnumberedsubsubsec Placement of lyrics between staves
@c TODO Add text from -user
+@c TODO Add new spacing properties, centering lyrics, etc
TBC
@node Stanzas
@node Stanzas with different rhythms
@unnumberedsubsubsec Stanzas with different rhythms
+Often, different stanzas of one song are put to one melody in slightly
+differing ways. Such variations can still be captured with
+@code{\lyricsto}.
+
@subsubheading Ignoring melismata
One possibility is that the text has a melisma in one stanza, but
@code{\set} and @code{\unset} to bracket the lyrics where melismata
are to be ignored.
+@subsubheading Adding syllables to grace notes
+
+By default, grace notes (e.g. via @code{\grace}) do not get assigned
+syllables when using @code{\lyricsto}, but this behavior can be
+changed:
+
+@lilypond[verbatim,ragged-right,quote]
+\relative c' {
+ f4 \appoggiatura a32 b4
+ \grace { f16[ a16] } b2
+ \afterGrace b2 { f16[ a16] }
+ \appoggiatura a32 b4
+ \acciaccatura a8 b4
+}
+\addlyrics {
+ normal
+ \set includeGraceNotes = ##t
+ case,
+ gra -- ce case,
+ after -- grace case,
+ \set ignoreMelismata = ##t
+ app. case,
+ acc. case.
+}
+@end lilypond
+
+@knownissues
+Like for @code{associatedVoice}, @code{includeGraceNotes} needs to be
+set at latest one syllable before the one which is to be put under a
+grace note. For the case of a grace note at the very beginning of a
+piece of music, consider using a @code{\with} or @code{\context}
+block:
+
+@lilypond[verbatim,ragged-right,quote]
+<<
+ \new Voice = melody \relative c' {
+ \grace { c16[( d e f] }
+ g1) f
+ }
+ \new Lyrics \with { includeGraceNotes = ##t }
+ \lyricsto melody {
+ Ah __ fa
+ }
+>>
+@end lilypond
+
@subsubheading Switching to an alternative melody
More complex variations in text underlay are possible. It is possible
Here, @code{alternative} is the name of the @code{Voice} context
containing the triplet.
-@c FIXME: make this easier to understand -vv
+@c TODO: make this easier to understand -vv
This command must be one syllable too early, before @q{Ty} in this
case. In other words, changing the associatedVoice happens one step
later than expected. This is for technical reasons, and it is not a
@rinternals{StanzaNumber}.
+@node Songs
+@subsection Songs
+
+@menu
+* References for songs::
+* Lead sheets::
+@end menu
+
+@node References for songs
+@unnumberedsubsubsec References for songs
+
+@c TODO chords, setting simple songs (LM), stanzas
+TBC
+
+@node Lead sheets
+@unnumberedsubsubsec Lead sheets
+
+Lead sheets may be printed by combining vocal parts and @q{chord mode};
+this syntax is explained in @ref{Chord notation}.
+
+@snippets
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{simple-lead-sheet.ly}
+
+@seealso
+Notation Reference:
+@ref{Chord notation}.
+
+
+@node Choral
+@subsection Choral
+
+@cindex anthems
+@cindex part songs
+@cindex oratorio
+@cindex SATB
+
+This section discusses notation issues that relate most directly
+to choral music. This includes anthems, part songs, oratorio,
+etc.
+
+@menu
+* References for choral::
+* Score layouts for choral::
+* Divided voices::
+@end menu
+
+@node References for choral
+@unnumberedsubsubsec References for choral
+
+Choral music is usually notated on two, three or four staves within
+a @code{ChoirStaff} group. Accompaniment, if required, is placed
+beneath in a @code{PianoStaff} group, which is usually reduced in
+size for @emph{a capella} choral works. The notes for each vocal
+part are placed in a @code{Voice} context, with each staff
+being given either a single vocal part (i.e., one @code{Voice}) or
+a pair of vocal parts (i.e., two @code{Voice}s).
+
+Words are placed in @code{Lyrics} contexts, either underneath each
+corresponding music staff, or one above and one below the music
+staff if this contains the music for two parts.
+
+Several common topics in choral music are described fully elsewhere:
+
+@itemize
+
+@item
+An introduction to creating an SATB vocal score can be found in
+the Learning Manual, see @rlearning{Four-part SATB vocal score}.
+
+@item
+Several templates suitable for various styles of choral music can
+also be found in the Learning Manual, see
+@rlearning{Vocal ensembles}.
+
+@item
+For information about @code{ChoirStaff} and @code{PianoStaff} see
+@ref{Grouping staves}.
+
+@item
+Shape noteheads, as used in Sacred Harp and similar notation, are
+described in @ref{Shape note heads}.
+
+@item
+When two vocal parts share a staff the stems, ties, slurs, etc., of
+the higher part will be directed up and those of the lower part
+down. To do this, use @code{\voiceOne} and @code{\voiceTwo}. See
+@ref{Single-staff polyphony}.
+
+@end itemize
+
+@predefined
+@code{\oneVoice},
+@code{\voiceOne},
+@code{\voiceTwo}.
+
+@seealso
+Learning Manual:
+@rlearning{Four-part SATB vocal score},
+@rlearning{Vocal ensembles}.
+
+Notation Reference:
+@ref{Context layout order},
+@ref{Grouping staves},
+@ref{Shape note heads},
+@ref{Single-staff polyphony}.
+
+Internals Reference:
+@rinternals{ChoirStaff},
+@rinternals{Lyrics},
+@rinternals{PianoStaff}.
+
+@node Score layouts for choral
+@unnumberedsubsubsec Score layouts for choral
+
+Choral music containing four staves, with or without piano
+accompaniment, is usually laid out with two systems per page.
+Depending on the page size, achieving this may require changes
+to several default settings. The following settings should be
+considered:
+
+@itemize
+
+@item
+The global staff size can be modified to change the overall size
+of the elements of the score. See @ref{Setting the staff size}.
+
+@item
+The distances between the systems, the staves and the lyrics can
+all be adjusted independently. See @ref{Vertical spacing}.
+
+@item
+The dimensions of the vertical layout variables can be displayed as
+an aid to adjusting the vertical spacing. This and other
+possibilities for fitting the music onto fewer pages are described
+in @ref{Fitting music onto fewer pages}.
+
+@item
+If the number of systems per page changes from one to two it is
+customary to indicate this with a system separator mark between
+the two systems. See @ref{Separating systems}.
+
+@item
+For details of other page formatting properties, see
+@ref{Page formatting}.
+
+@end itemize
+
+
+Dynamic markings by default are placed below the staff, but in
+choral music they are usually placed above the staff in order to
+avoid the lyrics. The predefined command @code{\dynamicUp} does
+this for the dynamic markings in a single @code{Voice} context.
+If there are many @code{Voice} contexts this predefined command
+would have to be placed in every one. Alternatively its expanded
+form can be used to place all dynamic markings in the entire score
+above their respective staves, as shown here:
+
+@lilypond[verbatim,quote]
+\score {
+ \new ChoirStaff <<
+ \new Staff {
+ \new Voice {
+ \relative c'' { g4\f g g g }
+ }
+ }
+ \new Staff {
+ \new Voice {
+ \relative c' { d4 d d\p d }
+ }
+ }
+ >>
+ \layout {
+ \context {
+ \Score
+ \override DynamicText #'direction = #UP
+ \override DynamicLineSpanner #'direction = #UP
+ }
+ }
+}
+@end lilypond
+
+@predefined
+@code{\dynamicUp}, @code{\dynamicDown}, @code{\dynamicNeutral}.
+
+@seealso
+Notation Reference:
+@ref{Changing spacing},
+@ref{Displaying spacing},
+@ref{Fitting music onto fewer pages},
+@ref{Page formatting},
+@ref{Score layout},
+See @ref{Separating systems},
+@ref{Setting the staff size},
+@ref{Using an extra voice for breaks},
+@ref{Vertical spacing}.
+
+Internals Reference:
+@rinternals{VerticalAxisGroup},
+@rinternals{StaffGrouper}.
+
+
+@node Divided voices
+@unnumberedsubsubsec Divided voices
+
+@cindex voices, divided
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{using-arpeggiobracket-to-make-divisi-more-visible.ly}
+
+@seealso
+Notation Reference:
+@ref{Expressive marks as lines}.
+
+
+@node Opera and stage musicals
+@subsection Opera and stage musicals
+
+The music, lyrics and dialogue to opera and stage musicals are
+usually set out in one or more of the following forms:
+
+@itemize
+
+@item
+A @emph{Conductors' Score} containing the full orchestral and vocal
+parts, together with libretto cues if there are spoken passages.
+
+@item
+@emph{Orchestral Parts} containing the music for the individual
+instruments of the orchestra or band.
+
+@item
+A @emph{Vocal Score} containing all vocal parts with piano
+accompaniment. The accompaniment is usually an orchestral
+reduction, and if so the name of the original orchestral instrument
+is often indicated. Vocal scores sometimes includes stage
+directions and libretto cues.
+
+@item
+A @emph{Vocal Book} containing just the vocal parts
+(no accompaniment), sometimes combined with the libretto.
+
+@item
+A @emph{Libretto} containing the extended passages of spoken
+dialogue usually found in musicals, together with the words to the
+sung parts. Stage directions are usually included. LilyPond can
+be used to typeset libretti but as they contain no music
+alternative methods may be preferable.
+
+@end itemize
+
+The sections in the LilyPond documentation which cover the topics
+needed to create scores in the styles commonly found in opera and
+musicals are indicated in the References below. This is followed
+by sections covering those techniques which are peculiar to
+typesetting opera and musical scores.
+
+@menu
+* References for opera and stage musicals::
+* Spoken music::
+* Dialogue over music::
+@end menu
+
+@node References for opera and stage musicals
+@unnumberedsubsubsec References for opera and stage musicals
+
+@itemize
+
+@item
+A conductors' score contains many grouped staves and lyrics. Ways
+of grouping staves is shown in @ref{Grouping staves}. To nest
+groups of staves see @ref{Nested staff groups}.
+
+@item
+The printing of empty staves in conductors' scores and vocal scores
+is often suppressed. To create such a @qq{Frenched score} see
+@ref{Hiding staves}.
+
+@item
+Writing orchestral parts is covered in @ref{Writing parts}.
+Other sections in the Specialist notation chapter may be relevant,
+depending on the orchestration used. Many instruments are
+transposing instruments, see @ref{Instrument transpositions}.
+
+@item
+If the number of systems per page changes from page to page it is
+customary to separate the systems with a system separator mark.
+See @ref{Separating systems}.
+
+@item
+For details of other page formatting properties, see
+@ref{Page formatting}.
+
+@item
+Character names are usually shown to the left of the staff when the
+staff is dedicated to that character alone. The instrument name can
+be used for this purpose. See @ref{Instrument names}.
+
+@item
+When two or more characters share a staff the character's name is
+usually printed above the staff at the start of every section
+applying to that character. This can be done with markup. The use
+of markup is covered fully in @ref{Text}. Often a specific font is
+used for this purpose, see @ref{Selecting font and font size}.
+
+@item
+Musical cues can be inserted with the @code{\cueDuring} predefined
+command. For details of its use see @ref{Formatting cue notes}.
+
+@item
+Dialogue cues and stage directions can be inserted with markup.
+See @ref{Text}. Extensive stage directions can be inserted with
+a section of stand-alone markup between two @code{\score} blocks.
+See @ref{Separate text}.
+
+@end itemize
+
+@predefined
+@code{\cueDuring},
+@code{\quoteDuring}.
+
+@seealso
+Musical Glossary:
+@rglos{cue-notes},
+@rglos{Frenched score},
+@rglos{Frenched staves},
+@rglos{transposing instrument}.
+
+Notation Manual:
+@ref{Grouping staves},
+@ref{Hiding staves},
+@ref{Instrument names},
+@ref{Instrument transpositions},
+@ref{Nested staff groups},
+@ref{Page formatting},
+@ref{Selecting font and font size},
+@ref{Separating systems},
+@ref{Text},
+@ref{Transpose},
+@ref{Writing parts},
+@ref{Writing text}.
+
+
+@node Spoken music
+@unnumberedsubsubsec Spoken music
+
+@cindex parlato
+@cindex Sprechgesang
+Such effects as @q{parlato} or @q{Sprechgesang} require performers to speak
+without pitch but still with rhythm; these are notated by cross
+note heads, as demonstrated in @ref{Special note heads}.
+
+@c TODO add "marking-notes-on-spoken-parts" snippet -vv
+@c add "showing the rhythm of a melody" snip
+@c add "one staff-line notation"
+@c add "improvisation" ref
+@c add "lyrics independents of notes" ref
+
+@node Dialogue over music
+@unnumberedsubsubsec Dialogue over music
+
+TBC
+
+
+@node Chants psalms and hymns
+@subsection Chants psalms and hymns
+
+@cindex chants
+@cindex psalms
+@cindex hymns
+@cindex religious music
+
+The music and words for chants, psalms and hymns usually follow a
+well-established format in any particular church. Although the
+formats may differ from church to church the type-setting problems
+which arise are broadly similar, and are covered in this section.
+
+@menu
+* References for chants and psalms::
+* Setting a chant::
+* Pointing a psalm::
+* Partial measures in hymn tunes::
+@end menu
+
+@node References for chants and psalms
+@unnumberedsubsubsec References for chants and psalms
+
+Typesetting Gregorian chant in various styles of ancient notation
+is described in @ref{Ancient notation}.
+
+@seealso
+Notation reference:
+@ref{Ancient notation}.
+
+
+@node Setting a chant
+@unnumberedsubsubsec Setting a chant
+
+Modern chant settings use modern notation with varying numbers of
+elements taken from ancient notation. Some of the elements and
+methods to consider are shown here.
+
+Chants often use quarter notes without stems to indicate the pitch,
+with the rhythm being taken from the spoken rhythm of the words.
+
+@lilypond[verbatim,quote]
+stemOff = { \override Staff.Stem #'transparent = ##t }
+
+\relative c' {
+ \stemOff
+ a'4 b c2 |
+}
+
+@end lilypond
+
+Chants often omit the bar lines or use shortened or dotted bar
+lines to indicate pauses in the music. To omit all bar lines from
+all staves remove the bar line engraver completely:
+
+@lilypond[verbatim,quote]
+\score {
+ \new StaffGroup <<
+ \new Staff {
+ \relative c'' {
+ a4 b c2 |
+ a4 b c2 |
+ a4 b c2 |
+ }
+ }
+ \new Staff {
+ \relative c'' {
+ a4 b c2 |
+ a4 b c2 |
+ a4 b c2 |
+ }
+ }
+ >>
+ \layout {
+ \context {
+ \Staff
+ \remove Bar_engraver
+ }
+ }
+}
+@end lilypond
+
+Bar lines can also be removed on a staff-by-staff basis:
+
+@lilypond[verbatim, quote]
+\score {
+ \new ChoirStaff <<
+ \new Staff
+ \with { \remove Bar_engraver } {
+ \relative c'' {
+ a4 b c2 |
+ a4 b c2 |
+ a4 b c2 |
+ }
+ }
+ \new Staff {
+ \relative c'' {
+ a4 b c2 |
+ a4 b c2 |
+ a4 b c2 |
+ }
+ }
+ >>
+}
+@end lilypond
+
+To remove bar lines from just a section of music treat it as a
+cadenza. If the section is long you may need to insert dummy
+barlines with @code{\bar ""} to show where the line should break.
+
+@lilypond[verbatim,quote,relative=2]
+a4 b c2 |
+\cadenzaOn
+a4 b c2
+a4 b c2
+\bar ""
+a4 b c2
+a4 b c2
+\cadenzaOff
+a4 b c2 |
+a4 b c2 |
+@end lilypond
+
+Rests or pauses in chants can be indicated by modified bar lines.
+
+@lilypond[verbatim, quote,relative=2]
+a4
+\cadenzaOn
+b c2
+a4 b c2
+\bar "'"
+a4 b c2
+a4 b c2
+\bar ":"
+a4 b c2
+\bar "dashed"
+a4 b c2
+\bar "||"
+@end lilypond
+
+Alternatively, the notation used in Gregorian chant for pauses or
+rests is sometimes used even though the rest of the notation is
+modern. This uses a modified @code{\breathe} mark:
+
+@lilypond[verbatim,quote]
+divisioMinima = {
+ \once \override BreathingSign #'stencil = #ly:breathing-sign::divisio-minima
+ \once \override BreathingSign #'Y-offset = #0
+ \breathe
+}
+divisioMaior = {
+ \once \override BreathingSign #'stencil = #ly:breathing-sign::divisio-maior
+ \once \override BreathingSign #'Y-offset = #0
+ \breathe
+}
+divisioMaxima = {
+ \once \override BreathingSign #'stencil = #ly:breathing-sign::divisio-maxima
+ \once \override BreathingSign #'Y-offset = #0
+ \breathe
+}
+finalis = {
+ \once \override BreathingSign #'stencil = #ly:breathing-sign::finalis
+ \once \override BreathingSign #'Y-offset = #0
+ \breathe
+}
+
+\score {
+ \relative c'' {
+ g2 a4 g
+ \divisioMinima
+ g2 a4 g
+ \divisioMaior
+ g2 a4 g
+ \divisioMaxima
+ g2 a4 g
+ \finalis
+ }
+ \layout {
+ \context {
+ \Staff
+ \remove Bar_engraver
+ }
+ }
+}
+@end lilypond
+
+Chants usually omit the time signature and often omit the clef too.
+
+@lilypond[verbatim,quote]
+\score {
+ \new Staff {
+ \relative c'' {
+ a4 b c2 |
+ a4 b c2 |
+ a4 b c2 |
+ }
+ }
+ \layout {
+ \context {
+ \Staff
+ \remove Bar_engraver
+ \remove Time_signature_engraver
+ \remove Clef_engraver
+ }
+ }
+}
+@end lilypond
+
+Chants for psalms in the Anglican tradition are usually either
+@emph{single}, with 7 bars of music, or @emph{double}, with two lots
+of 7 bars. Each group of 7 bars is divided into two halves,
+corresponding to the two halves of each verse, usually separated by
+a double bar line. Only whole and half notes are used. The 1st bar
+in each half always contains a single chord of whole notes. This is
+the @qq{reciting note}.
+
+Some approaches to setting such a chant are shown in the first of
+the following snippets, and another example can be seen in the
+templates, see @qq{Psalms} in @rlearning{Vocal ensembles}.
+
+@snippets
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{chant-or-psalms-notation.ly}
+
+Canticles and other liturgical texts may be set more freely, and
+may use notational elements from ancient music. Often the words
+are shown underneath and aligned with the notes. If so, the notes
+are spaced in accordance with the syllables rather than the notes'
+durations.
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{ancient-notation-template----modern-transcription-of-gregorian-music.ly}
+
+@seealso
+Learning Manual:
+@rlearning{Visibility and color of objects}.
+
+Notation Reference:
+@ref{Ancient notation},
+@ref{Bar lines},
+@ref{Modifying context plug-ins},
+@ref{Typesetting Gregorian chant},
+@ref{Unmetered music},
+@ref{Visibility of objects}.
+
+
+@node Pointing a psalm
+@unnumberedsubsubsec Pointing a psalm
+
+The words to a Anglican psalm are usually printed in separate
+verses underneath the chant. See the Anglican psalm template in
+the Learning Manual to see how to use mark-up to center the chant
+and place the verses centered underneath. Marks are inserted
+in the words to show how they should be fitted to the chant.
+Single chants (with 7 bars) are repeated for every verse. Double
+chants (with 14 bars) are repeated for every pair of verses.
+
+Each verse is divided into two halves. An asterisk or a colon
+is frequently used to indicate this division. This corresponds
+to the double bar line in the music. The words before the colon
+are sung to the first 3 bars of music; the words after the colon
+are sung to the last four bars.
+
+Single bar lines (or in some psalters an inverted comma or similar
+symbol) are inserted between words to indicate where the bar lines
+in the music fall. In markup mode a single bar line can be entered
+with the bar check symbol, @code{|}. Other symbols may require
+glyphs from the @code{fetaMusic} fonts. For details, see
+@ref{Fonts}.
+
+Where there is one whole note in a bar all the words corresponding
+to that bar are recited on that one note in speech rhythm. Where
+there are two notes in a bar there will usually be only one or two
+corresponding syllables. If there are more that two syllables a
+dot is usually inserted to indicate where the change in note occurs.
+
+In some psalters an asterisk is used to indicate a break in a
+recited section instead of a comma, and stressed or slightly
+lengthened syllables are indicated in bold text. Others use an
+accent over the syllable to indicate stress.
+
+The use of markup to center text, and arrange lines in columns is
+described in @ref{Formatting text}.
+
+Most of these elements are shown in one or other of the two verses
+in the template, see @qq{Psalms} in @rlearning{Vocal ensembles}.
+
+@seealso
+Learning Manual:
+@rlearning{Vocal ensembles}.
+
+Notation Reference:
+@ref{Fonts},
+@ref{Formatting text}.
+
+
+@node Partial measures in hymn tunes
+@unnumberedsubsubsec Partial measures in hymn tunes
+
+Hymn tunes frequently start and end every line of music with
+partial measures so that each line of music corresponds exactly
+with a line of text. This requires a @code{\partial} command at
+the start of the music and @code{\bar "|"} or @code{\bar "||"}
+commands at the end of each line.
+
+@lilypondfile[verbatim,lilyquote,ragged-right,texidoc,doctitle]
+{hymn-template.ly}
+
+
+@node Ancient vocal music
+@subsection Ancient vocal music
+
+Ancient vocal music is supported, as explained in @ref{Ancient notation}.
+
+@c TODO
+
+@c Add "Printing both the ancient and the modern clef in vocal music" snippet,
+@c and "Transcription of Ancient music with incipit" snippet. -vv
+
+@seealso
+Notation Reference:
+@ref{Ancient notation}.
+
+
projects / lilypond.git / blobdiff