TODO
- * mail .po files to gnu translation project
- * convince xgettext my name is <janneke@gnu.org> iso
- <fred@botervlieg.flower> :-)
- * create user-friendly input format for multiple languages?
-
-ISSUES -- please read this before doing too much real translating...
-
- * please don't run make po/po-update with gnu gettext < 0.10.35
- * encapsulate locale strings in _( ) or _f ( )
- * fix/standardise messages
- - it's silly to translate wrong strings
- - no leading/trailing punctuation in strings: e.g.
- _ ("foo found") iso _ ("foo found.), _ ("foo found.\n), ...
- - no leading/trailing whitespace in strings
-
- - Think about translation issues.
- In a lot of cases,it's better to translate a whole message
- the english grammar mustn't be imposed on the transator.
- So, iso
- _ ("stem at") + moment.str () + _("doen't fit in beam")
- have
- _f ("stem at %s doen't fit in beam", moment.str ())
- ?
-
- Otoh:
- en: can't open: `foo.ly'
- nl: kan `foo.ly' niet openen (1)
- kan niet openen: `foo.ly'* (2)
- niet te openen: `foo.ly'* (3)
-
- The first nl message, although gramatically and stylish correct,
- is not friendly for parsing by humans (even if they speak dutch).
- I guess we'd prefer something like (2) or (3)...
-
- - don't modularise too much; a lot of words cannot be translated
- without context.
- it's probably safe to treat most occurences of words like
- stem, beam, crescendo as separately translatable words.
-
- * don't! translate/gettextify:
- - debug strings
- - output (ps) strings
-
-
-SOLVED/HOWTO
- * because i never install LilyPond, i made these links:
-
- ln -s $LILYPOND_SOURCEDIR/po/out/nl.mo
- /usr/share/locale/nl/LC_MESSAGES/lilypond.mo
- ln -s $LILYPOND_SOURCEDIR/po/out/it.mo
- /usr/share/locale/it/LC_MESSAGES/lilypond.mo
-
- then simply type, e.g.
-
- LANG=nl lilypond -h
-
- * (howto?) avoid keep translating for moving target
- - make po-update
- - mv po/out/*.po po (manually!)
- - edit po/*.po
- - make -C po
- - make show-po-update LANGUAGE=xx
+
+See also README for general instructions.
+
+FIX OR STANDARDISE TARGETS
+
+* extract translatable strings from source code to `po/out/': at toplevel, do:
+
+ make po
+ make -C po po-update (or do `make po-update' at toplevel)
+
+* if there are no errors (a list of changes against `po/' directory may be
+ displayed, that's ok), do
+
+ cp po/out/*.po po/
+
+ copy the template file for translating to a new language LANG: do
+
+ cp po/out/lilypond.po po/LANG.po
+
+* and edit your favorite po/LANG.po using a dedicated tool:
+
+ kbabel po/fi.po
+ gtranslator po/fi.po
+
+ Especially, look for fuzzy and untranslated entries. At the bottom of
+ the file may accumulate the list of obsolete translations, which may
+ help to translate some changed entries and may be safely dropped out.
+
+* because I never install LilyPond, I made these links:
+
+ ln -s $LILYPOND_SOURCEDIR/po/out/nl.mo
+ $PREFIX/usr/share/locale/nl/LC_MESSAGES/lilypond.mo
+ ln -s $LILYPOND_SOURCEDIR/po/out/it.mo
+ $PREFIX/usr/share/locale/it/LC_MESSAGES/lilypond.mo
+
+ $PREFIX is the --prefix you passed to configure.
+
+ then simply type, e.g.
+
+ LANG=nl lilypond -h
+
+ note that your favorite language should also be listed in locales, check
+
+ locale -a