Helping with the documentation

[Graham Percival]

Hi all,

I'm getting a bit overwhelmed working on the documentation, so I'm 
asking for help.  I've posted a list of tasks to the -devel mailist.  
Some of them require very little previous knowledge of LilyPond, and 
are actually a great way to learn.  You can read them here:
http://lists.gnu.org/archive/html/lilypond-devel/2006-04/msg00231.html

Apart from those tasks, I have on more request: please don't forward an 
email from -user to -devel or the bug mailist with the message "you 
should improve the docs in this area".  If you think an email contains 
important information or clarification of the documentation, please 
take the time to propose *exact* changes to the documentation.  If you 
are personally involved in the discussion, then you probably know more 
about this area than I do.  This is certainly true if the issue 
involves anything that is covered in Chapter 7 Instrument-specific 
notation.

Finally, some background about me: I'm just a normal user.  In August 
2004, I volunteered to become Documentation Editor, because I speak 
English as a first language and have some time to contribute.  I didn't 
program LilyPond, nor do I have any special training in music 
publication.  I play cello and viola at a high level (as a university 
undergraduate performer); my knowledge about printed music comes from 
reading music.  I have seen a lot of string music, and some orchestral 
scores, but I have very little knowledge of vocal music, piano, guitar, 
and the like.  If you play any of those instruments -- anything which 
is in Chapter 7 -- then I practically guarantee that you know more 
about using LilyPond to create music for those instruments.

For information about proposing changes to the docs, see
http://lilypond.org/web/devel/participating/documentation-adding

Thanks,
- Graham