lilypond-devel
[Top][All Lists]
Advanced

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

Re: [PATCH]: Doc: NR @knownissue for partCombine + spanners (issue462907


From: tdanielsmusic
Subject: Re: [PATCH]: Doc: NR @knownissue for partCombine + spanners (issue4629073)
Date: Sun, 26 Jun 2011 22:00:52 +0000

A few more nitpicking typos - some I missed first time through, some you
missed when dealing with my earlier comments :)

I'm happy for you to push after fixing these.  Thanks!

Trevor



http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode775
Documentation/notation/simultaneous.itely:775: @code{Voice} is printed.
Stem directions are set up & down accordingly
space

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode814
Documentation/notation/simultaneous.itely:814: Both parts have identical
notes in the third measure, only one instance
so only

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode816
Documentation/notation/simultaneous.itely:816: automatically, depending
whether the parts are playing solo or in
depending on whether

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode817
Documentation/notation/simultaneous.itely:817: unison. When needed in
polyphony situations, the first part (with
space

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode819
Documentation/notation/simultaneous.itely:819: @code{two}) always gets
@qq{down} stems. In solo situations, the first
space

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode867
Documentation/notation/simultaneous.itely:867: notes as two separate
voices, even if they can be combined to a chord or
into a chord

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode879
Documentation/notation/simultaneous.itely:879: @code{\partcombineSoloI}
and @code{\partcombineSoloIOnce} prints only
print

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode880
Documentation/notation/simultaneous.itely:880: voice one, and marks it
as a @qq{Solo}.
mark

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode883
Documentation/notation/simultaneous.itely:883: @code{\partcombineSoloII}
or @code{\partcombineSoloIIOnce} prints only
print

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode884
Documentation/notation/simultaneous.itely:884: voice two and marks it as
a @qq{Solo}.
mark

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode888
Documentation/notation/simultaneous.itely:888: the functions of the
commands above, and reverts back to the standard
revert

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode954
Documentation/notation/simultaneous.itely:954: typeset @code{a2} more
than once that measure.
in that measure.

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode956
Documentation/notation/simultaneous.itely:956: @code{\partcombine} only
knows when a note starts in a @code{Voice}, it
@code{Voice};

http://codereview.appspot.com/4629073/diff/1003/Documentation/notation/simultaneous.itely#newcode957
Documentation/notation/simultaneous.itely:957: cannot for example,
remember if a note in one @code{Voice} has already
cannot, for example,

http://codereview.appspot.com/4629073/



reply via email to

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