(this list will be posted to lilypond-user from time to time; it will
not be posted on a wiki or anything like that, since I'm the only person
who should be modifying the list)
Lilypond Odd Jobs
-----------------
ONE-SHOT JOBS (estimated time: between 1/2 and 2 hours)
- create example for automatic accidental examples that demonstrates
everything
- special markup command examples (note head styles, rotation, etc:
complicated stuff to show off some possibilities). Maybe as LSR instead
of manual.
- document (manual or LSR) adding command-line arguments to lilypond scores:
http://www.mail-archive.com/lilypond-user@gnu.org/msg16042.html
http://lists.gnu.org/archive/html/lilypond-user/2006-10/msg00271.html
- document (manual or LSR) adding arguments to \include:
http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00642.html
- document (manual or LSR) first/last page header commands:
http://www.mail-archive.com/lilypond-user@gnu.org/msg24949.html
- document (manual or LSR) multiple tags:
http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00635.html
- prettify the main "snippets" page of the docs.
input/lsr/LSR.ly
http://lilypond.org/doc/v2.11/input/lsr/collated-files
TECHNICALLY ADVANCED
- convert-ly bugs and tips
- preprocessor docs
- musicxml: document current features, limitations
- musicxml: programming. (it's currently not supported)
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
- go through ly/music-functions-init.ly and add a doc string to every
function listed.
- Some type of doc that outlined the lexical construction of Lilypond
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
