X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnotation%2Fstaff.itely;h=2ac12942588040d1c86c482b8be26963a7f7ef95;hb=1b11dc0cb1bec0e353773aac6b8afba9030f88c4;hp=56f493617d36022ac048837f9981d54f986bef60;hpb=d25fbff2e29563ae3e2bd8f3a6d7269fd1164393;p=lilypond.git diff --git a/Documentation/notation/staff.itely b/Documentation/notation/staff.itely index 56f493617d..2ac1294258 100644 --- a/Documentation/notation/staff.itely +++ b/Documentation/notation/staff.itely @@ -1172,20 +1172,12 @@ Installed Files: @knownissues - Only the contents of the first @code{Voice} occurring in an -@code{\addQuote} command will be considered for quotation, so -@code{@var{music}} cannot contain @code{\new} and -@code{\context Voice} statements that would switch to a different -Voice. - -Quoting grace notes is broken and can even cause LilyPond to -crash. - -Quoting nested triplets may result in poor notation. - -In earlier versions of LilyPond (pre 2.11), @code{addQuote} was -written entirely in lower-case letters: @code{\addquote}. +@code{\addQuote} command will be considered for quotation, so if the music +expression contains @code{\new} or @code{\context Voice} +statements, their contents will not be quoted. Quoting grace notes +is unsupported and may cause LilyPond to crash whereas quoting nested +triplets may result in poor notation. @node Formatting cue notes @@ -1227,7 +1219,7 @@ d,4 r a r The @code{\cueClef} command can also be used with an explict @code{CueVoice} context if a change of clef is required and will print -an appropriately sized clef for the cue notes. The @code{\cueClefUnset} +an appropriately sized clef for the cue notes. The @code{\cueClefUnset} command can then be used to switch back to the original clef, again with an appropriately sized clef. @@ -1257,7 +1249,7 @@ d,,4 r a r For more complex cue note placement, e.g including transposition, or inserting cue notes from multiple music sources the @code{\cueDuring} or -@code{\cueDuringWithClef} commands can be used. These are more +@code{\cueDuringWithClef} commands can be used. These are more specialized form of @code{\quoteDuring}, see @ref{Quoting other voices} in the previous section. @@ -1274,10 +1266,10 @@ and @end example The music from the corresponding measures of the @code{@var{quote name}} -is added as @code{CueVoice} context and occurs simultaneously with the -@code{@var{music}}, which creates a polyphonic situation. The +is added as a @code{CueVoice} context and occurs simultaneously with the +@code{@var{music}}, which then creates a polyphonic situation. The @code{@var{direction}} takes the argument @code{UP} or @code{DOWN}, and -corresponds to first and second voices respectively determining how +corresponds to the first and second voices respectively, determining how the cue notes are printed in relation to the other voice. @lilypond[verbatim,quote] @@ -1300,9 +1292,7 @@ oboeNotes = \relative c'' { @end lilypond @noindent -In the above example, the @code{Voice} context had to be -explicitly declared, or else the entire music expression would -belong to the @code{CueVoice} context. + It is possible to adjust which aspects of the music are quoted with @code{\cueDuring} by setting the @code{quotedCueEventTypes} @@ -1311,6 +1301,10 @@ tie-event beam-event tuplet-span-event)}, which means that only notes, rests, ties, beams and tuplets are quoted, but not articulations, dynamic marks, markup etc. +In this example, the @code{Voice} context must be +explicitly declared, or else the entire music expression would +belong to the @code{CueVoice} context. + @lilypond[verbatim,quote] oboeNotes = \relative c'' { r2 r8 d16(\f f e g f a) @@ -1476,6 +1470,7 @@ Notation Reference: @ref{Quoting other voices}, @ref{Instrument transpositions}, @ref{Instrument names}, +@ref{Clef}, @ref{Musical cues}, @ref{Using tags}.