http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1350 Documentation/notation/rhythms.itely:1350: partial measure @emph{before} the start of the next full measure. What about "where @code{@var{duration}} is the duration that will be added before the first measure. In other words, it is the @emph{remaining} length of the partial measure @emph{before} the start of the first full measure." ? http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1353 Documentation/notation/rhythms.itely:1353: \time 6/8 On 2012/01/09 05:08:58, Graham Percival wrote:
huh?! why is this easier to understand than \partial 4 ?
+1 http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1355 Documentation/notation/rhythms.itely:1355: e8 | a4 c8 b[ c b] | On 2012/01/09 05:08:58, Graham Percival wrote:
what on earth does manual beaming have to do with a \partial? How
does that
improve this example?
+1 http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1358 Documentation/notation/rhythms.itely:1358: The partial @var{duration} can be any value less than a full measure: I'm not sure about "partial duration" thing. But i like the "value" part. http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely#newcode1363 Documentation/notation/rhythms.itely:1363: r4 e8 | a4 c8 b[ c b] | i think original example was better because it showed use of 8*3 construct. http://codereview.appspot.com/5520056/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
