Generally ok, but I don't know why you're changing the translations
before the English docs are done.


http://codereview.appspot.com/2735044/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):

http://codereview.appspot.com/2735044/diff/1/Documentation/notation/pitches.itely#newcode538
Documentation/notation/pitches.itely:538: for quarter tones in various
languages; here the prefixes
why remove the hyphen?  It should be "quarter-tones", or more strictly
"quarter-tone accidentals".

http://codereview.appspot.com/2735044/diff/1/Documentation/notation/pitches.itely#newcode564
Documentation/notation/pitches.itely:564: Western classical music, also
referred to as @q{Common Practice
On 2010/10/29 10:15:46, Trevor Daniels wrote:
It would be good to have a Glossary entry for CPP

Yes, and then make this a @notation{Common Practice Period}.

http://codereview.appspot.com/2735044/diff/1/Documentation/notation/world.itely
File Documentation/notation/world.itely (right):

http://codereview.appspot.com/2735044/diff/1/Documentation/notation/world.itely#newcode28
Documentation/notation/world.itely:28: @c TODO: adapt & expand. -vv
Delegate this to somebody who knows about this stuff, and make it more
obvious that we could use help with this.  Eliminate the TODO, and just
add a new issue for "write stuff about non-common period practice tuning
systems".

http://codereview.appspot.com/2735044/diff/1/Documentation/notation/world.itely#newcode55
Documentation/notation/world.itely:55: @c TODO: can we include the
actual accidentals in this table?
Eliminate the TODO, and what do you actually mean by this?

http://codereview.appspot.com/2735044/diff/1/Documentation/notation/world.itely#newcode138
Documentation/notation/world.itely:138: tailored as discussed in
@ref{Note names in other languages}.
This part will need changing.

http://codereview.appspot.com/2735044/

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to