Doc: translations: manually update syntax (1358)

Doc: translations: manually update syntax (1358)

[Graham Percival (old account), 2010-11-13 17:22:44]

Translation Meister: here's a fix for 1358.  ok to push?

I don't know why this issue has been hanging around for 3 week... I mean,
editing .ly code and @funindex entries isn't precisely difficult!

[pacovila, 2010-11-14 07:11:44]

On 2010/11/13 17:22:44, Graham Percival wrote:
> Translation Meister: here's a fix for 1358.  ok to push?
> 
> I don't know why this issue has been hanging around for 3 week... I mean,
> editing .ly code and @funindex entries isn't precisely difficult!

Push if you want to, but besides version strings all these changes are already
done, see comment on staff.itely.  It's not a matter of difficulty; rather the
commit went unnoticed.  The commit is in lilypond/translation branch and still
(as of Nov 14th) not merged into master.

[pacovila, 2010-11-14 07:13:08]

Graham: here are my comments. I will not close the issue until all other
languages are revised, but for German it is done. Thanks

http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/frette...
File Documentation/de/notation/fretted-strings.itely (right):

http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/frette...
Documentation/de/notation/fretted-strings.itely:11: @c \version "2.13.39"
Original has 2.13.36 here; while this is technically correct, translators prefer
to have these strings in sync. The --to=2.13.36 option does this.

http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/staff....
File Documentation/de/notation/staff.itely (right):

http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/staff....
Documentation/de/notation/staff.itely:682: Man kann auch den @code{\Staff
\RemoveEmptyStaves}-Befehl einsetzen,
Gernam translator already did this and all other changes on this file on
623a785573, dated 2010-11-06, the commit was entitled as an update, so maybe the
patch is redundant for this file at least.

http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/text.i...
File Documentation/de/notation/text.itely (right):

http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/text.i...
Documentation/de/notation/text.itely:1280: \musicglyph #"accordion.discant"
same as for staff.itely before; all changes already applied

[Graham Percival (old account), 2010-11-14 20:52:20]

On 2010/11/14 07:13:08, pacovila wrote:
> Graham: here are my comments. I will not close the issue until all other
> languages are revised, but for German it is done. Thanks

I'll close this patch request, at least.


>
http://codereview.appspot.com/3092041/diff/1/Documentation/de/notation/frette...
> Documentation/de/notation/fretted-strings.itely:11: @c \version "2.13.39"
> Original has 2.13.36 here; while this is technically correct, translators
prefer
> to have these strings in sync. The --to=2.13.36 option does this.

Once the current manually-upgrading mess is sorted out, this won't be a problem
-- doc editors (and translators) will never run convert-ly; it will be run by
programmers, on all the doc files at once.  The --to option should not be used.

Hmm, I just realized that translators _might_ want to run convert-ly manually,
if there's a merge conflict with a recent addition to master.  Ick.  I'll make a
note to write policy for this (issue 1397).