Status: Accepted
Owner: v.villenave
Labels: Type-Documentation Priority-Medium Patch
New issue 1371 by v.villenave: Documentation: note names language
http://code.google.com/p/lilypond/issues/detail?id=1371
Before I forget, here's the current status for \language command
documentation.
NR 1.1.1 pitches "Note names in other languages" needs to be partially
rewritten. However, prior to doing that, I'd like to
- remove the @warning about how to organize \include instructions:
http://codereview.appspot.com/2791041/ should hopefully make it irrelevant.
- remove arabic.ly from the note name languages. Again, a patch exists:
http://codereview.appspot.com/2755041/
However, this raises more questions:
- should we rename "Non-Western note names and accidentals"
into "Non-Western notation and tuning systems"?
- should we get rid of this subsection altogether, and move it to "World
music"?
- should we, on the contrary, make it more clear that LilyPond equally
(well, ideally) supports "Common Practice Period" (CPP) languages and
non-CPP languages? (Which not only includes non-Western music, but some
traditional types of music, etc.)
[Whilst the "non-CPP" wording looks ugly and confusing to me, "Word music"
is hardly better: it does have an unfortunate Western-centric,
neo-colonialist, not to mention snobish, aspect.]
Note for myself: on -user there have been talks about Balinese note names.
To be investigated.
http://lists.gnu.org/archive/html/lilypond-user/2010-10/msg00693.html
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
