Follow-up Comment #2, patch #6700 (project duplicity):
Hmm, I haven't been able to find a link that suits duplicity's setup (no
autotools). But here's the basic gist (I'll use French (fr) in my examples):
Ideally translators can work with the source package, but doing so in CVS is
possible.
In the po directory, running "intltool-update --pot" will generate the pot if
one is interested in just that, else "intltool-update fr" will generate the
pot file and an untranslated fr.po. Running intltool will require at least
Makevars and POTFILES.in (so it knows where to look for translatable strings
and it knows what values to insert into new po files).
Once a translator has the fr.po, they will be able to fill in strings and
eventually kick it back to you. You drop it in the po directory, and
everything works.
To generate mo files from the po files (as it seems you want to do at
tarball-creation-time), run msgfmt on each po file. You can also msgunfmt on
a mo file to get a po again.
To actually use an installed translation, you need to have the installed
locale file (run "locale-gen fr_FR.UTF-8" to create a
French-speaker-living-in-France-and-using-UTF-8 one). Then just set your LANG
variable to the locale ("export LANG=fr_FR.UTF-8") and run duplicity.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?6700>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Duplicity-tracker mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
