[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-tracker] [patch #6700] Make duplicity translatable

From: Michael Terry
Subject: [Duplicity-tracker] [patch #6700] Make duplicity translatable
Date: Mon, 29 Dec 2008 17:22:49 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5

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

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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]