Re: Doc: NR cross-staff (issue3782042)

[tdanielsmusic]

The content looks fine, but it should be rearranged a little to match
the existing style of the documentation.


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

http://codereview.appspot.com/3782042/diff/1/Documentation/notation/keyboards.itely#newcode173
Documentation/notation/keyboards.itely:173: time of the switch.  If
necessary, add spacer rests to
No, it means write in the third person, not the second.  (The LM is
written in a more chatty style; here the style should be impersonal.)

http://codereview.appspot.com/3782042/diff/1/Documentation/notation/keyboards.itely#newcode195
Documentation/notation/keyboards.itely:195: @end lilypond
This example and the point it makes is a useful addition, but I would
prefer to see the original example retained to show in the starkest
fashion how staves should be changed manually, with this one added later
to show the possibility of collisions.  Note also that the established
policy is to explain the point being made first with the illustrative
example following.

http://codereview.appspot.com/3782042/diff/1/Documentation/notation/keyboards.itely#newcode205
Documentation/notation/keyboards.itely:205: Automatic collision
resolution is suspended for beams, slurs
Better joined to previous sentence: "The stems overlap the intervening
line of dynamics because automatic collision.."

http://codereview.appspot.com/3782042/diff/1/Documentation/notation/keyboards.itely#newcode209
Documentation/notation/keyboards.itely:209: Resolve the resulting
collisions manually, when necessary,
Third person

http://codereview.appspot.com/3782042/