@cindex easy notation
@cindex Hal Leonard
-The `easyplay' note head includes a note name inside the head. It is
-used in music aimed at beginners.
+The `easy play' note head includes a note name inside the head. It is
+used in music aimed at beginners:
@lilypond[singleline,verbatim,26pt]
\score {
@seealso
-@internalsref{OttavaBracket}.
+@internalsref{OttavaSpanner}.
@refbugs
@lilypond[verbatim]
\score { \notes \relative c'' {
#(set-time-signature 9 8 '(2 2 2 3))
- g8-[ g-] d-[ d-] g-[ g-] a8-[-( bes g-]-) |
+ g8[ g] d[ d] g[ g] a8[( bes g]) |
#(set-time-signature 5 8 '(3 2))
a4. g4
}
\property Staff.NoteCollision \override
#'merge-differently-dotted = ##t
g8 g8
- } \\ { g8.-[ f16-] g8.-[ f16-] }
+ } \\ { g8.[ f16] g8.[ f16] }
>
@end lilypond
@lilypond[fragment,relative,verbatim]
\context Staff {
- r4 r8-[ g' a r8-] r8 g-[ | a-] r8
+ r4 r8[ g' a r8] r8 g[ | a] r8
}
@end lilypond
@lilypond[fragment,relative,verbatim]
\context Staff {
- f8-[ r16 f g a-]
- f8-[ r16 \property Voice.stemLeftBeamCount = #1 f g a-]
+ f8[ r16 f g a]
+ f8[ r16 \property Voice.stemLeftBeamCount = #1 f g a]
}
@end lilypond
@cindex @code{stemRightBeamCount}
@lilypond[relative=1,verbatim,noindent]
- c16-[ c c c c c c c-]
+ c16[ c c c c c c c]
\property Voice.subdivideBeams = ##t
- c16-[ c c c c c c c-]
+ c16[ c c c c c c c]
\property Score.beatLength = #(ly:make-moment 1 8)
- c16-[ c c c c c c c-]
+ c16[ c c c c c c c]
@end lilypond
@cindex subdivideBeams
between the note heads. This behavior can be tuned through the object
property @code{auto-knee-gap}.
+Normally, line breaks are forbidden when beams cross bar lines. This
+behavior can be changed by setting @code{allowBeamBreak}.
+
+@cindex @code{allowBeamBreak}
+@cindex beams and line breaks
+
@cindex beams, kneed
@cindex kneed beams
@cindex auto-knee-gap
\property Voice.autoBeamSettings
\override #'(end * * * *) = #(ly:make-moment 3 8)
% rather show case where it goes wrong
- %\time 12/8 c'8 c c c16 c c c c c c-[ c c c-] c8-[ c-] c4
+ %\time 12/8 c'8 c c c16 c c c c c c[ c c c] c8[ c] c4
\time 12/8 c'8 c c c16 c c c c c c c c c c8 c c4
@end lilypond
It is not possible to specify beaming parameters that act differently in
They are entered using parentheses:
@lilypond[fragment,verbatim,center]
- f'-( g'-)-( a'-) a'8-[ b'-(-] a'4 g'2 f'4-)
- <<c' e'>>2-( <<b d'>>2-)
+ f'( g')( a') a'8[ b'(] a'4 g'2 f'4)
+ <<c' e'>>2( <<b d'>>2)
@end lilypond
@lilypond[fragment,relative,verbatim]
\slurUp
\property Voice.Stem \set #'length = #5.5
- g'8-(g g4-)
+ g'8(g g4)
\property Voice.Slur \set #'attachment = #'(stem . stem)
- g8-( g g4-)
+ g8( g g4)
@end lilypond
If a slur would strike through a stem or beam, the slur will be moved
@lilypond[fragment,relative,verbatim]
\stemUp \slurUp
- d32-( d'4 d8..-)
+ d32( d'4 d8..)
\property Voice.Slur \set #'attachment = #'(stem . stem)
- d,32-( d'4 d8..-)
+ d,32( d'4 d8..)
@end lilypond
@refcommands
respectively:
@lilypond[fragment,verbatim,center,relative]
- \time 6/4 c'-\( d-( e-) f-( e-) d-\)
+ \time 6/4 c'-\( d( e) f( e) d-\)
@end lilypond
Typographically, the phrasing slur behaves almost exactly like a
@seealso
-@internalsref{TempoEvent}.
+@internalsref{MetronomeChangeEvent}.
@lilypondfile[notexidoc]{script-abbreviations.ly}
+The meanings of these shorthands can be changed: see
+@file{ly/script-init.ly} for examples.
+
+
The script is automatically placed, but if you need to force
directions, you can use @code{_} to force them down, or @code{^} to
put them up:
c''4^^ c''4_^
@end lilypond
-
-
-
Other symbols can be added using the syntax
@var{note}@code{-\}@var{name}, e.g. @code{c4-\fermata}. Again, they
can be forced up or down using @code{^} and @code{_}:
You can use the thumb-script to indicate that a note should be
played with your thumb (used in cello music):
-@lilypond[verbatim, singleline, fragmnt]
- <<a' a''-3>>8-(_\thumb-[ <<b' b''-3>>-)_\thumb
- <<c'' c'''-3>>-(_\thumb <<d'' d'''-3>>-)_\thumb-]
+@lilypond[verbatim, singleline, fragment]
+ <<a' a''-3>>8(_\thumb[ <<b' b''-3>>)_\thumb
+ <<c'' c'''-3>>(_\thumb <<d'' d'''-3>>)_\thumb]
@end lilypond
Fingerings for chords can also be added to individual notes
@node Grace notes
@subsection Grace notes
+
+@c should have blurb about accaciatura / appogiatura
+
@cindex @code{\grace}
@cindex ornaments
@cindex grace notes
-Grace notes are ornaments that are written out:
-
+Grace notes are ornaments that are written out, like accaciatura and
+appogiatura notes.
@lilypond[relative=2,verbatim,fragment] c4 \grace c16 c4 \grace {
[c16 d16] } c4
@end lilypond
-In normal notation, grace notes take up no logical
-time in a measure. Such an idea is practical for normal notation, but
-is not strict enough to put it into a program. The model that LilyPond
-uses for grace notes internally is that all timing is done in two
-steps:
-
-Every point in musical time consists of two rational numbers: one
-denotes the logical time, one denotes the grace timing. The above
-example is shown here with timing tuples:
+From the point of view of typesetting, their characteristic is that
+grace notes take up take up no logical time in a measure. Internally,
+timing for grace notes is done using a second time. Every point in
+musical time consists of two rational numbers: one denotes the logical
+time, one denotes the grace timing. The above example is shown here
+with timing tuples:
@lilypond[]
\score { \notes \relative c''{
c4^"(0,0)" \grace c16_" "_"(1/4,-1/16)" c4^"(1/4,0)" \grace {
- c16_"(2/4,-1/8)"-[ d16^"(2/4,-1/16)" ] } c4_" "_"(2/4,0)"
+ c16_"(2/4,-1/8)"[ d16^"(2/4,-1/16)" ] } c4_" "_"(2/4,0)"
}
\paper { linewidth = 12.\cm }
}
every eighth grace note:
@lilypond[relative=2,verbatim,fragment]
-< \context Staff = SA { e4 \grace { c16-[ d e f-] } e4 }
- \context Staff = SB { c'4 \grace { g8-[ b-] } c4 } >
+< \context Staff = SA { e4 \grace { c16[ d e f] } e4 }
+ \context Staff = SB { c'4 \grace { g8[ b] } c4 } >
@end lilypond
Unbeamed eighth notes and shorter by default have a slash through the
-stem. This can be controlled with object property @code{stroke-style} of
-@internalsref{Stem}. For proper matching of override and reverts of
-such properties, it is necessary to use a Scheme function.
+stem. These notes are called accaciaturas, and should generally be
+played as short as possible. An appogiatura takes a fixed fraction of
+the main note, is and denoted without a slash.
+
+Such slashless notes are obtained by setting the object property
+@code{stroke-style} of the @internalsref{Stem} object. For proper
+matching of override and reverts of such properties, it is necessary
+to use a Scheme function.
The following fragment overrides the default formatting Grace style stems:
@example
@lilypond[fragment,verbatim]
\relative c'' \context Voice {
- \grace c8 c4 \grace { c16-[ c16-] } c4
+ \grace c8 c4 \grace { c16[ c16] } c4
\grace {
\property Voice.Stem \override #'stroke-style = #'()
c16
@lilypond[fragment,verbatim, relative=2]
\context Voice {
< { d1^\trill ( }
- { s2 \grace { c16-[ d-] } } >
+ { s2 \grace { c16[ d] } } >
)c4
}
@end lilypond
\relative c'' \context Voice {
\slurUp
\grace {
- a4-( }
- ) a4 a4-( a2-)
+ a4( }
+ ) a4 a4( a2)
\slurBoth
\grace {
\slurUp
- a4-( }
- ) a4 a4-( a2-)
+ a4( }
+ ) a4 a4( a2)
\slurBoth
}
@end lilypond
< f''1 { s4 s4-\< s4-\! \> s4-\! } >
@end lilypond
This may give rise to very short hairpins. Use @code{minimum-length}
-in @internalsref{Voice}.@internalsref{HairPin} to lengthen them, for
+in @internalsref{Voice}.@internalsref{Hairpin} to lengthen them, for
example:
@example
included with the distribution as @inputfileref{input/test,stem-cross-staff.ly}.
Dynamics are not centered, but kludges do exist. See
-@inputfileref{input/templates,piano-dynamics.ly}.
+@inputfileref{input/template,piano-dynamics.ly}.
@cindex cross staff stem
@cindex stem, cross staff
@cindex choral score
A complete example of a SATB score setup is in the file
-@inputfileref{input/template,satb}.
+@inputfileref{input/template,satb.ly}.
@seealso
@internalsref{LyricCombineMusic}, @internalsref{Lyrics}, and
-@inputfileref{input/template,satb}.
+@inputfileref{input/template,satb.ly}.
@refbugs
Then set the @internalsref{LyricsVoice} contexts to names starting with
that identity followed by a dash. In the preceding example, the
@internalsref{Voice} identity is @code{duet}, so the identities of the
-@internalsref{LyricsVoices} are marked @code{duet-1} and @code{duet-2}:
+@internalsref{LyricsVoice}s are marked @code{duet-1} and @code{duet-2}:
@example
\context LyricsVoice = "duet-1" @{
Hi, my name is bert. @}
Bar numbers can collide with the @internalsref{StaffGroup} bracket, if
there is one at the top. To solve this, the
-@internalsref{padding} property of @internalsref{BarNumber} can be
+@code{padding} property of @internalsref{BarNumber} can be
used to position the number correctly.
@node Instrument names
\context Staff <
\context Voice=one \partcombine Voice
\context Thread=one \relative c'' {
- g a-( b-) r
+ g a( b) r
}
\context Thread=two \relative c'' {
g r4 r f
@cindex Petrucci
@cindex mensural
-@c [TODO: write introduction on ancient notation]
+@c [TODO: write more comprehensive introduction on ancient notation]
+
+Support for ancient notation is still under heavy development.
+Regardless of all of the current limitations (see the bugs section
+below for details), it currently includes features for mensural
+notation and Gregorian Chant notation. There is also limited support
+for figured bass notation.
+
+Many graphical objects provide a @code{style} property, see
+@ref{Ancient note heads}, @ref{Ancient accidentals}, @ref{Ancient
+rests}, @ref{Ancient clefs}, @ref{Ancient flags} and @ref{Ancient time
+signatures}. By manipulating such a grob property, the typographical
+appearance of the affected graphical objects can be accomodated for a
+specific notation flavour without need for introducing any new
+notational concept.
@menu
* Ancient note heads::
* Ancient rests::
* Ancient clefs::
* Ancient flags::
+* Ancient time signatures::
+@end menu
+
+Other aspects of ancient notation can not that easily be expressed as
+in terms of just changing a style property of a graphical object.
+Therefore, some notational concepts are introduced specifically for
+ancient notation, see @ref{Custodes}, @ref{Divisiones},
+@ref{Ligatures}, and @ref{Figured bass}.
+
+@menu
* Custodes::
* Divisiones::
* Ligatures::
* Figured bass::
@end menu
+If this all is way too much of documentation for you, and you just
+want to dive into typesetting without worrying too much about the
+details on how to customize a context, then you may have a look at the
+predefined contexts (see @ref{Vaticana style contexts}). Use them to
+set up predefined style-specific voice and staff contexts, and
+directly go ahead with the note entry.
+
+@menu
+* Vaticana style contexts::
+@end menu
+
+@refbugs
+
+Ligatures need special spacing that has not yet been implemented. As
+a result, there is too much space between ligatures most of the time,
+and line breaking often is unsatisfactory. Also, lyrics do not
+correctly align with ligatures.
+
+Accidentals must not be printed within a ligature, but instead need to
+be collected and printed in front of it.
+
+Augmentum dots within ligatures are currently not handled correctly.
+
@node Ancient note heads
@subsection Ancient note heads
@cindex note heads
+@syntax
+
For ancient notation, a note head style other than the @code{default}
style may be chosen. This is accomplished by setting the @code{style}
property of the NoteHead object to the desired value (@code{baroque},
such there is no need to explicitly set the note head style. Still,
the note head style can be set e.g. to @code{vaticana_punctum} to
produce punctum neumes. Similarly, a mensural ligature engraver is
-used to automatically assemble mensural ligatures. See section
+used to automatically assemble mensural ligatures. See
@ref{Ligatures} for how ligature engravers work.
@seealso
@cindex accidentals
+@syntax
+
Use the @code{style} property of grob @internalsref{Accidental} to
select ancient accidentals. Currently supported styles are
@code{mensural}, @code{vaticana}, @code{hufnagel} and @code{medicaea}.
controlled by the @code{style} property of the
@internalsref{KeySignature} grob.
+@seealso
+
+@ref{Pitches}, @ref{Chromatic alterations} and @ref{Accidentals} give
+a general introduction into the use of accidentals. @ref{Key
+signature} gives a general introduction into the use of key
+signatures.
+
@node Ancient rests
@subsection Ancient rests
@cindex rests
+@syntax
+
Use the @code{style} property of grob @internalsref{Rest} to select
ancient accidentals. Currently supported styles are @code{classical},
@code{neo_mensural} and @code{mensural}. @code{classical} differs
There are no rests in Gregorian Chant notation; instead, it uses
@ref{Divisiones}.
+@seealso
+
+@ref{Rests} gives a general introduction into the use of rests.
+
@node Ancient clefs
@subsection Ancient clefs
@cindex clefs
-LilyPond supports a variety of clefs, many of them ancient.
+@syntax
-For modern clefs, see section @ref{Clef}. For the percussion clef, see
-section @ref{Percussion staves}. For the @code{TAB} clef, see section
-@ref{Tablatures}.
+LilyPond supports a variety of clefs, many of them ancient.
The following table shows all ancient clefs that are supported via the
@code{\clef} command. Some of the clefs use the same glyph, but
differ only with respect to the line they are printed on. In such
cases, a trailing number in the name is used to enumerate these clefs.
Still, you can manually force a clef glyph to be typeset on an
-arbitrary line, as described in section @ref{Clef}. The note printed
-to the right side of each clef in the example column denotes the
-@code{c'} with respect to that clef.
+arbitrary line, as described in @ref{Clef}. The note printed to the
+right side of each clef in the example column denotes the @code{c'}
+with respect to that clef.
@multitable @columnfractions .3 .3 .3 .1
Petrucci used C clefs with differently balanced left-side vertical
beams, depending on which staffline it is printed.
+@seealso
+
+For modern clefs, see @ref{Clef}. For the percussion clef, see
+@ref{Percussion staves}. For the @code{TAB} clef, see
+@ref{Tablatures}.
+
@node Ancient flags
@subsection Ancient flags
@cindex flags
+@syntax
+
Use the @code{flag-style} property of grob @internalsref{Stem} to
select ancient flags. Besides the @code{default} flag style,
currently only @code{mensural} style is supported:
music, the default flag style should be used. There are no flags in
Gregorian Chant notation.
+
+@node Ancient time signatures
+@subsection Ancient time signatures
+
+@cindex time signatures
+
+@syntax
+
+There is limited support for mensural time signatures. Currently, the
+glyphs are hard-wired to particular time fractions. In other words,
+to get a particular mensural signature glyph with the @code{\time n/m}
+command, @code{n} and @code{m} have to be chosen according to the
+following table:
+
+@lilypond
+\score {
+ \notes {
+ \property Score.timing = ##f
+ \property Score.barAlways = ##t
+ s_\markup { "$\\backslash$time 4/4" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural4/4" }
+ s
+ s_\markup { "$\\backslash$time 2/2" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural2/2" }
+ s
+ s_\markup { "$\\backslash$time 6/4" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural6/4" }
+ s
+ s_\markup { "$\\backslash$time 6/8" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural6/8" }
+ \break
+ s_\markup { "$\\backslash$time 3/2" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural3/2" }
+ s
+ s_\markup { "$\\backslash$time 3/4" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural3/4" }
+ s
+ s_\markup { "$\\backslash$time 9/4" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural9/4" }
+ s
+ s_\markup { "$\\backslash$time 9/8" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural9/8" }
+ \break
+ s_\markup { "$\\backslash$time 4/8" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural4/8" }
+ s
+ s_\markup { "$\\backslash$time 2/4" }
+ ^\markup { " " \musicglyph #"timesig-neo\_mensural2/4" }
+ \break
+ }
+ \paper {
+ indent = 0.0
+ raggedright = ##t
+ \translator {
+ \StaffContext
+ \remove Staff_symbol_engraver
+ \remove Clef_engraver
+ \remove Time_signature_engraver
+ }
+ }
+}
+@end lilypond
+
+Use the @code{style} property of grob @internalsref{TimeSignature} to
+select ancient time signatures. Currently supported styles are
+@code{neo_mensural} and @code{mensural}. The above table uses the
+@code{neo_mensural} style. This style is appropriate e.g. for the
+incipit of transcriptions of mensural pieces. The @code{mensural}
+style mimicks the look of historical printings of the 16th century.
+
+@inputfileref{input/test,time.ly} gives an overview over all available
+ancient and modern styles.
+
+@seealso
+
+@ref{Time signature} gives a general introduction into the use of time
+signatures.
+
+@refbugs
+
+Mensural signature glyphs are currently mapped to time fractions in a
+hard-wired way. This mapping is sensible, but still arbitrary: given
+a mensural time signature, the time fraction represents a modern meter
+that usually will be a good choice when transcribing a mensural piece
+of music. For a particular piece of mensural music, however, the
+mapping may be unsatisfactory. In particular, the mapping assumes a
+fixed transcription of durations (e.g. brevis = half note in 2/2,
+i.e. 4:1). Some glyphs (such as the alternate glyph for 6/8 meter)
+are currently not at all accessible through the @code{\time} command.
+
+Mensural time signatures are supported typographically, but not yet
+musically. The internal representation of durations is currently
+based on a purely binary system; a ternary division such as 1 brevis =
+3 semibrevis (tempus perfectum) or 1 semibrevis = 3 minima (cum
+prolatione maiori) is not correctly handled: event times in ternary
+modes will be badly computed, resulting e.g. in horizontally
+misaligned note heads, and bar checks are likely to erroneously fail.
+
+The syntax and semantics of the @code{\time} command for mensural
+music is subject to change.
+
@node Custodes
@subsection Custodes
like the @emph{editio vaticana}. There are different custos glyphs
used in different flavours of notational style.
+@syntax
+
For typesetting custodes, just put a @internalsref{Custos_engraver} into the
@internalsref{Staff} context when declaring the @code{\paper} block,
as shown in the following example:
@seealso
-
@internalsref{Custos} and @inputfileref{input/regression,custos.ly}.
Therefore, @code{gregorian-init.ly} also defines @code{\virgula} and
@code{\caesura}:
-
@lilypondfile[notexidoc]{divisiones.ly}
+@refcommands
+
+@cindex @code{\virgula}
+@code{\virgula},
+@cindex @code{\caesura}
+@code{\caesura},
+@cindex @code{\divisioMinima}
+@code{\divisioMinima},
+@cindex @code{\divisioMaior}
+@code{\divisioMaior},
+@cindex @code{\divisioMaxima}
+@code{\divisioMaxima},
+@cindex @code{\finalis}
+@code{\finalis}.
+
@seealso
@internalsref{BreathingSign}, @internalsref{BreathingSignEvent},
There is limited support for white mensural ligatures. The
implementation is still experimental; it currently may output strange
warnings or even crash in some cases or produce weird results on more
-complex ligatures. To engrave white mensural ligatures, in the paper
-block the @internalsref{Mensural_ligature_engraver} has to be put into
-the @internalsref{Voice} context, and remove the
+complex ligatures.
+
+@syntax
+
+To engrave white mensural ligatures, in the paper block the
+@internalsref{Mensural_ligature_engraver} has to be put into the
+@internalsref{Voice} context, and remove the
@internalsref{Ligature_bracket_engraver}:
@example
}
@end lilypond
+
@node Gregorian square neumes ligatures
@subsubsection Gregorian square neumes ligatures
@end multitable
+@syntax
Unlike most other neumes notation systems, the input language for
neumes does not necessarily reflect directly the typographical
@end multitable
+@refcommands
+
+The following head prefixes are supported:
+
+@cindex @code{\virga}
+@code{\virga},
+@cindex @code{\stropha}
+@code{\stropha},
+@cindex @code{\inclinatum}
+@code{\inclinatum},
+@cindex @code{\auctum}
+@code{\auctum},
+@cindex @code{\descendens}
+@code{\descendens},
+@cindex @code{\ascendens}
+@code{\ascendens},
+@cindex @code{\oriscus}
+@code{\oriscus},
+@cindex @code{\quilisma}
+@code{\quilisma},
+@cindex @code{\deminutum}
+@code{\deminutum}.
+
+Head prefixes can be accumulated, though restrictions apply. For
+example, either @code{\descendens} or @code{\ascendens} can be applied
+to a head, but not both to the same head.
+
+@cindex @code{\pes}
+@cindex @code{\flexa}
+Two adjacent heads can be tied together with the @code{\pes} and
+@code{\flexa} infix commands for a rising and falling line of melody,
+respectively.
+
@refbugs
Scandicus Deminutus: Punctum Auctum Ascendens overlaps with
Trigonus: apply equal spacing, regardless of pitch.
+Flexa and similar figurae: the left appendix should be adjusted with
+respect to the position of this head (on staffline or on staffspace)
+and the vertical position of the subsequent head.
+
@node Figured bass
@subsection Figured bass
Slash notation for alterations is not supported.
+@node Vaticana style contexts
+@subsection Vaticana style contexts
+
+@cindex VaticanaVoiceContext
+@cindex VaticanaStaffContext
+
+The predefined @code{VaticanaVoiceContext} and
+@code{VaticanaStaffContext} can be used to easily engrave a piece of
+Gregorian Chant in the style of the Editio Vaticana. These contexts
+initialize all relevant context properties and grob properties to
+proper values. With these contexts, you can immediately go ahead
+entering the chant, as the following short excerpt demonstrates:
+
+@lilypond[raggedright,verbatim,noindent]
+\include "gregorian-init.ly"
+\score {
+ \addlyrics
+ \context VaticanaVoice {
+ \property Score.BarNumber \set #'transparent = ##t
+ \notes {
+ \[ c'( c' \flexa a \] \[ a \flexa \deminutum g) \] f \divisioMinima
+ \[ f( \pes a c' c' \pes d') \] c' \divisioMinima \break
+ \[ c'( c' \flexa a \] \[ a \flexa \deminutum g) \] f \divisioMinima
+ }
+ }
+ \context Lyrics \lyrics {
+ San- ctus, San- ctus, San- ctus
+ }
+}
+@end lilypond
+
@node Contemporary notation
@section Contemporary notation
@lilypondfile[notexidoc]{cluster.ly}
-By default, @internalsref{Cluster_engraver} is in the
+By default, @internalsref{Cluster_spanner_engraver} is in the
@internalsref{Voice} context. This allows putting ordinary notes and
clusters together in the same staff, even simultaneously. In such a
case no attempt is made to automatically avoid collisions between
@internalsref{ClusterSpanner}, @internalsref{ClusterSpannerBeacon},
@inputfileref{input/regression,cluster.ly},
-@internalsref{Cluster_engraver}, and @internalsref{ClusterNoteEvent}.
+@internalsref{Cluster_spanner_engraver}, and @internalsref{ClusterNoteEvent}.
@refbugs
Syntax errors for markup mode are confusing.
+Markup texts cannot be used in the titling of the @code{\header}
+field. Titles are made by La@TeX{}, so La@TeX{} commands should be used
+for formatting.
+
@cindex staff distance
@cindex between staves, distance
@cindex staffs per page
-
+@cindex space between staves
The height of each system is determined automatically by LilyPond, to
keep systems from bumping into each other, some minimum distances are
half a NHW:
@lilypond[fragment, verbatim, relative=2]
- c2 c4. c8 c4. c16-[ c-] c4. c8 c8 c8 c4 c4 c4
+ c2 c4. c8 c4. c16[ c] c4. c8 c8 c8 c4 c4 c4
@end lilypond
The most common shortest duration is determined as follows: in every
projects / lilypond.git / blobdiff