[Top][All Lists]

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

Re: Doc: NR cross-staff (issue3782042)

From: k-ohara5a5a
Subject: Re: Doc: NR cross-staff (issue3782042)
Date: Thu, 23 Dec 2010 21:17:02 +0000

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
File Documentation/notation/keyboards.itely (right):
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?
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
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.

reply via email to

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