Lilypond Odd Jobs (mostly documentation)

[Graham Percival]

Are you interested in helping LilyPond?  There are many tasks that are 
available which do not have time to do ourselves.  Some of these require 
a fair amount of technical knowledge, but many of them only require a 
moderate amount of lilypond skill.


Lilypond Odd Jobs
-----------------

Cameron Horsburgh has agreed to monitor the lilypond-user maillist 
documentation issues.


ONE-SHOT JOBS (estimated time: 30min - 2 hrs each)
- create example for automatic accidental examples that demonstrates 
everything
- add avoid-slur settings to everything in scm/script.scm
- preprocessor docs
- convert-ly bugs and tips
- musicxml: current features, limitations
- pdf chapter headings (in sidebar)
- special markup command examples (note head styles, rotation, etc: 
complicated stuff to show off some possibilities).  Maybe as LSR or 
input/test/ instead of manual.
- add one-line examples to 8.1.6 Overview of text markup
commands.  See
http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00143.html


TECHNICAL ABILITY REQUIRED
- integrate LSR:
http://lists.gnu.org/archive/html/lilypond-devel/2006-08/msg00146.html
(once LSR is done)
- clean up input/test/
- copy any useful examples from input/regression into input/test/


GENERAL EDITING / JANITORIAL:
- check manual for current correctness (does it make sense, is the info 
up-to-date, etc)
- verify anything in the "bugs" sections
- standardize # signs
http://lists.gnu.org/archive/html/lilypond-devel/2006-10/msg00180.html
- avoid future tense
http://lists.gnu.org/archive/html/lilypond-devel/2006-01/msg00076.html


ADVANCED
- So, another thing for the todo list
is to do through ly/music-functions-init.ly  and add a doc string to every
function listed.
- ideally, add examples as well; see 12.1.7  Overview of available music 
functions.  See
http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00143.html
- Some type of doc. that oulined the lexical construction of Lilypond 
would be helpful.