In general I agree with Carl's comments.  I've suggested in a couple of
places where I'd like to see the IR material truncated.  The full
description of the properties should go in the NR, perhaps in an
appendix if you think it's too technical.


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

http://codereview.appspot.com/3031041/diff/30001/Documentation/notation/spacing.itely#newcode1496
Documentation/notation/spacing.itely:1496: @code{VerticalAxisGroup} are:
VerticalAxisGroup is a unique object (in this context), so should not be
preceded by "the", although this might be debatable.  I'd prefer to see
"the VerticalAxisGroup layout object", which is incontravertably
correct.  Same for the names of other grobs.

http://codereview.appspot.com/3031041/diff/30001/lily/axis-group-interface.cc
File lily/axis-group-interface.cc (right):

http://codereview.appspot.com/3031041/diff/30001/lily/axis-group-interface.cc#newcode780
lily/axis-group-interface.cc:780: "The following properties of the
@code{VerticalAxisGroup}"
On 2010/11/11 04:37:18, Carl wrote:

The interface page in the IR *might* be the right place
to put it, but I think it is better to have the full
description in the NR, and a short description in
the IR.

I agree.  If the material in the NR appears too technical, or spoils the
flow, it would be in keeping with the general style of the NR to place
it in an appendix of the NR, not in the IR.

http://codereview.appspot.com/3031041/diff/30001/lily/axis-group-interface.cc#newcode798
lily/axis-group-interface.cc:798: " whitespace between two items,
measured in staff-spaces."
Stop here.  Repeat with rest in NR.

http://codereview.appspot.com/3031041/diff/30001/lily/axis-group-interface.cc#newcode805
lily/axis-group-interface.cc:805: " between the @emph{reference points}
of the two items"
Stop here.  Repeat with rest in NR.  (Ditto for other properties)

http://codereview.appspot.com/3031041/

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to