lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

DOC: fix NR 1.6.3 Formatting Cue Notes (Issue 1762) (issue4808051)


From: ColinPKCampbell
Subject: DOC: fix NR 1.6.3 Formatting Cue Notes (Issue 1762) (issue4808051)
Date: Fri, 22 Jul 2011 02:03:44 +0000

Reviewers: ,

Message:
Addresses Reinhold's comment re issue 1762

Description:
DOC: fix NR 1.6.3 Formatting Cue Notes

Moves comment about explicitly creating a Voice, to the proper example.

Please review this at http://codereview.appspot.com/4808051/

Affected files:
  M Documentation/notation/staff.itely


Index: Documentation/notation/staff.itely
diff --git a/Documentation/notation/staff.itely b/Documentation/notation/staff.itely index 5344ab2b866ba8181d93084f9df01c385740487b..d0d6da753649a38d09665ce71da27ac036946984 100644
--- a/Documentation/notation/staff.itely
+++ b/Documentation/notation/staff.itely
@@ -1292,9 +1292,6 @@ 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}
@@ -1319,6 +1316,10 @@ oboeNotes = \relative c'' {
 }
 @end lilypond

+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.
+
 Markup can be used to show the name of the quoted instrument.  Also,
 if the cue notes require a change in clef, this can be done manually but
 the original clef should also be restored manually at the end of the cue





reply via email to

[Prev in Thread] Current Thread [Next in Thread]