lilypond-devel
[Top][All Lists]
Advanced

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

Re: Doc: NR 4.4.1: Rewrite. (issue2642043)


From: joeneeman
Subject: Re: Doc: NR 4.4.1: Rewrite. (issue2642043)
Date: Tue, 26 Oct 2010 22:28:16 +0000


http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):

http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely#newcode1624
Documentation/notation/spacing.itely:1624: size) will always reset all
its default key-values.
Everything from the subsubheading until here applies to any grob
property with an alist (eg. Beam 'details, Slur 'details,
NonMusicalPaperColumn 'line-break-system-details). It may be more
appropriate (long-term) to put this detailed discussion elsewhere.

http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely#newcode1662
Documentation/notation/spacing.itely:1662:
@code{after-last-staff-spacing}).
I find this wording a little confusing, since
\override VerticalAxisGroup #'next-staff-spacing ...
has a quite different effect from
\override StaffGrouper #'...

That is, overriding next-staff-spacing does not "override" any
StaffGrouper properties for the usual use of "override" in lilypond.

http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely#newcode1672
Documentation/notation/spacing.itely:1672: system.
default-next-staff-spacing also applies to staves which are not part of
a staff group

http://codereview.appspot.com/2642043/diff/1/Documentation/notation/spacing.itely#newcode1679
Documentation/notation/spacing.itely:1679: either side.  Adjacent
staff-like contexts should have
I'm not sure how precise you want to be here, but this isn't quite true:
if the upper staff, for example, has a very low note then a lyrics line
with CENTER affinity might be placed closer to the lower staff.

Also, by "equidistant between the ... staves," you mean "equidistant
between the refpoints of the staves," right?

http://codereview.appspot.com/2642043/



reply via email to

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