1 ISSUES -- please read this before doing too much real translating...
3 * encapsulate locale strings in _( ) or _f ( )
4 * fix/standardise messages
5 - it's silly to translate wrong strings
6 - no leading/trailing punctuation in strings: e.g.
7 _ ("foo found") iso _ ("foo found.), _ ("foo found.\n), ...
8 - no leading/trailing whitespace in strings
10 - Think about translation issues.
11 In a lot of cases,it's better to translate a whole message
12 the english grammar mustn't be imposed on the transator.
14 _ ("stem at") + moment.str () + _("doen't fit in beam")
16 _f ("stem at %s doen't fit in beam", moment.str ())
20 en: can't open: `foo.ly'
21 nl: kan `foo.ly' niet openen (1)
22 kan niet openen: `foo.ly'* (2)
23 niet te openen: `foo.ly'* (3)
25 The first nl message, although gramatically and stylish correct,
26 is not friendly for parsing by humans (even if they speak dutch).
27 I guess we'd prefer something like (2) or (3)...
29 - don't modularise too much; a lot of words cannot be translated
31 it's probably safe to treat most occurences of words like
32 stem, beam, crescendo as separately translatable words.
34 * don't! translate/gettextify:
39 * native speakers (naïeve sprekerds) that make/take care of {it,..}.po
40 * concurrently update Documentation/tex/computer.data
41 * convince xgettext my name is <janneke@gnu.org> iso
42 <fred@botervlieg.flower> :-)
43 * create user-friendly input format for multiple languages?
46 * because i never install LilyPond, i made these links:
48 ln -s $LILYPOND_SOURCEDIR/po/out/nl.mo
49 /usr/share/locale/nl/LC_MESSAGES/lilypond.mo
50 ln -s $LILYPOND_SOURCEDIR/po/out/it.mo
51 /usr/share/locale/it/LC_MESSAGES/lilypond.mo
53 then simply type, e.g.
57 * (howto?) avoid keep translating for moving target
59 - mv po/out/*.po po (manually!)
62 - make show-po-update LANGUAGE=xx