On 2010/12/23 07:57:58, Valentin Villenave wrote:
Oh I see: it's not a bug, it's a feature :)
There is some of that. I hope the text does not sound dismissive. I was trying to sound humble: crossing staves is difficult; LilyPond might need your help. There are several un-necessary collisions shown in the tracker that I would call bugs, and hope LP can someday handle with a bit more sophistication. 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 On 2010/12/23 07:57:58, Valentin Villenave wrote:
Doc guidelines [...] avoid addressing the reader.
CG4.4.5 says "do not explicitly refer to the reader/user ... there is no-one else", and I thought that meant drop the extra words in "[-The-user-should-] add spacer rests". We are *always* addressing the reader/user, no? http://codereview.appspot.com/3782042/diff/1/Documentation/notation/keyboards.itely#newcode204 Documentation/notation/keyboards.itely:204: Notice that the stems overlap the intervening line of dynamics. Doc guidelines do say avoid fluff. "[-Notice-that-] The stems overlap..." http://codereview.appspot.com/3782042/diff/1/Documentation/notation/keyboards.itely#newcode206 Documentation/notation/keyboards.itely:206: and other spanners that connect notes on different staves, On 2010/12/23 13:14:22, pkx166h wrote:
In which case should this addition be an @warning?
I think not here. Most @warnings are things the user needs to know on first use of a feature, but would likely miss in simple text instruction. Here, we want to help users who are already crossing staves, and who have come back to the manual for help with collisions. The image with an overlapping beam helps the reader find this text better than a "Note:" box. http://codereview.appspot.com/3782042/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
