[ckan-dev] Translating plugins & custom translations how-to

Ian Ward ian at excess.org
Tue Nov 19 15:39:17 UTC 2013


On Tue, Nov 19, 2013 at 8:47 AM, Samuele Santi
<samuele.santi at trentorise.eu> wrote:
>
>
> Of course, it would be possible to create a paster command that does
> something like this:
>
> - - aggregate translations from core + plugins (this part needs some
> care, as the correct procedure is to merge POTs first, and then merge
> translations in the newly created POT)
>
> - - install new translation PO files in ckan.i81n_directory (and compile
> them to MO)
>

This sounds good, but does it handle changes to the upstream
translations well? Do you copy all the translations into your
extension, overriding later changes made upstream?

How do you handle translations for different sets of plugins? Are
there any problems with sharing translations with this scheme?

Ian



More information about the ckan-dev mailing list