Re: Document changing default rest position in NR 1.2.2

[Arle Lommel]

Thanks. Given that Colin has created a new tracker do you still want me to 
submit to the LSR? I'm happy to do so, but just want to make sure that it 
doesn't create any problems now that Colin has done that if I *also* submit to 
LSR. If you tell me to go ahead, I will try to do so in the next few days and 
also comment on the tracker so readers there are aware.

Shall I submit a bug about the lack of LSR mention in the documentation? That 
one I probably shouldn't add to the LSR ;-) Or is your awareness of it enough.

Thanks much for guiding me through this. I'd like to be more active in 
contributing back to the project and this helps me understand the best ways.

Arle


On 2012 Dec 20, at 11:58 , "Trevor Daniels" <address@hidden> wrote:

> 
> Arle, you wrote Thursday, December 20, 2012 9:58 AM
> 
>> Thanks for letting me know. If that is the process, then probably 
>> the documentation on how to make "small additions" itself needs 
>> to be updated to clarify what gets submitted where, since I was 
>> trying to follow the guidelines here:
>> 
>> http://lilypond.org/doc/v2.17/Documentation/contributor/documentation-suggestions
> 
> That's a valid point.  The LSR ought to be mentioned here.
> 
>> With regard to the location, I proposed it for that section to keep it 
>> parallel with the content in 
>> http://lilypond.org/doc/v2.16/Documentation/notation/writing-rests#index-positioning-multi_002dmeasure-rests
>>  
>> which already describes the essentially identical override technique 
>> for full-measure rests. 
> 
> Yes, that section was originally extracted from the LSR 
> (see http://lsr.dsi.unimi.it/LSR/Item?id=591
> although I see it was later extended without being updated in 
> the LSR) using exactly the method I described:
> 
>> Thanks for the suggestion, Arle.  The correct way to add this to
>> the documentation is to submit your example, with appropriate
>> explanatory text, to the LSR, tagging it for docs, rhythms and
>> tweaks and overrides.  This is the way users can add material to
>> the documentation - it will then appear automatically in the
>> Snippets list.
>> 
>> Once that is done, the doc writers can easily add it to the
>> selected snippets in the position you suggest.  Overrides such
>> as the one you suggest are (with very few exceptions) not 
>> included in the main text of Chapter 1 of the Notation Reference;
>> there would simply be far too many equally useful candidates.
>> 
> Trevor