2 Notes about Bacula translations.
3 --------------------------------
7 To edit .po files, I recommend poedit, downloadable at http://www.poedit.org/ .
11 To refresh bacula.pot and *.po, when some strings have been added, modified or
12 removed from the sources files, run:
17 To refresh Bacula source files list (POTFILES.in), when a source file is
18 added or removed from the repository, run:
19 # make gen-potfiles && make update-po
20 Note, the make gen-potfiles should not be done very often, in fact,
21 it is probably better to edit POTFILES.in manually to prevent unwanted
22 files from getting in the list.
26 To add a new translation language (e.g. German), add a new line to LINGUAS
27 containing the language code (e.g. de), then run:
28 # msginit -l <full locale> (e.g. "# msginit -l de_DE")
30 Open the newly created file in an editor (e.g. de.po), and look for this line:
31 "Project-Id-Version: ...\n"
32 If it still look like this:
33 "Project-Id-Version: PACKAGE VERSION\n"
35 "Project-Id-Version: Bacula 1.38\n"
37 You may also want to correct the language team to:
38 "Language-Team: German <bacula-devel@lists.sourceforge.net>\n"
40 Finally, add <language code>.mo (e.g. de.mo) to .cvsignore, and don't forget to
42 # cvs add <language code>.po <language code>.gmo
46 For more informations, see gettext manual:
47 http://www.gnu.org/software/gettext/manual/
51 Nicolas Boichat <nicolas@boichat.ch>, August 2005