1 * Requirement for Translators and developers: gettext-0.11.5
3 http://www.gnu.org/software/gettext/
5 Read the doc. However, the logic used is a bit different
10 Contact fvwm-workers@fvwm.org
18 * For creating a new catalogs, say LL_CC (e.g., fr, zh_CN):
20 - Edit configure.in and add LL_CC to ALL_LINGUAS
21 - run autoconf and ./configure (with your usual options) and check that
22 the new "lang" appear in the list of "lang"
23 Locale msg: prefix/share/locale ... LL_CC ...
25 - create a domain.LL_CC.po file for all files domain.pot:
27 msginit -i fvwm.pot -l LL_CC -o fvwm.LL_CC.po
28 msginit -i FvwmTaskBar.pot -l LL_CC -o FvwmTaskBar.LL_CC.po
31 The --no-translator option can be useful under certain situation
32 (e.g., you do not use the LL_CC locale). In this case you should
33 edit the files you have created and in particular set the
36 - Then, you can start the translation of fvwm.LL_CC.po,
37 FvwmTaskBar.LL_CC.po ...etc
39 NOTE: You should "make domain.LL_CC.gmo" before make install
40 and test your translation visually!
44 - make [all] should do nothing (but, maybe, recreating the
45 Makefile). "make install" install! But see the previous NOTE.
47 - The following (re)build everything (safe):
51 - If some messages have changed in some source files in "domain":
53 make domain.pot-update
55 update domain.pot. Then you can
59 to get the new messages for translation. After translation:
61 make domain.LL_CC.gmo # create a binary mo file from the po one
69 make update-gmo # build all the binary gmo files
71 * Creation of a new domain: ask the fvwm-workers@fvwm.org.
75 - Update ALL_DOMAINS in configure.in
76 - Add NEW_DOMAIN in configure.in
77 - Create po/$NEW_DOMAIN.pot (xgettext) and add it to EXTRA_DIST
78 (todo: remove this step)
79 - Set the files which contains msg NEW_DOMAIN = file1 file2 ...
80 in the beginning of po/Makefile.am
81 - Add $(srcdir)/$(NEW_DOMAIN).pot: and $(NEW_DOMAIN).pot-update:
83 - Update $(POFILES): and update-po: in po/Makfile.am
84 (todo: remove this step)