[ckan-dev] Can extensions provide their own *.po files?

Nigel Babu nigel.babu at okfn.org
Fri May 30 12:18:14 UTC 2014


Hi David,

Extensions can provide their own extensions. But the .po files need to be
merged. Vitor did some work around this[1].

I'm hoping Vitor will jump in with more details when he sees this email.

[1]
https://github.com/okfn/ckanext-mx/blob/master/bin/build-combined-ckan-mo.sh

On Thu, May 29, 2014 at 02:48:05PM -0400, David Megginson wrote:
> If I create a custom theme for CKAN that includes text not in the original
> CKAN templates, is there a way to translate it without having to edit core
> (essentially, to fork CKAN) by directly editing the files in ckan/i18n/?
>
> For example, let's say that my custom template lists the followers for each
> dataset.  I can include something like this in the Jinja2 template:
>
> <h3>{{ _('People following this dataset') }}</h3>
>
> Now, how do I translate that to "Ceux qui suivent ce jeu de données" or
> "Personen, die diese Datenmenge folgen"? Is there any way that theming
> extensions can provide their own *.po files?
>
>
> Thanks, David

> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev


--
Nigel Babu
Developer, Open Knowledge



More information about the ckan-dev mailing list