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

[Vitor Baptista]

Hi Ian,

As far as I understood, whenever you run this "make-i18n" paster command,
it'll recompile all languages and put them on the i18n_folder. So, if
something changes on upstream, you can simply run it again, and it should
work.

I like this approach, even though it's still a bit hacky. Ideally, IMO,
every time CKAN starts, it would do this process by itself (looking into
plugins, checking which have i18n files, and merging them), so we wouldn't
need to have a new paster command. But it's a great improvement over what
we have.

Cheers,


2013/11/19 Ian Ward <ian at excess.org>

> 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
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>



-- 

Vítor Baptista

Developer  |  http://vitorbaptista.com |
LinkedIn<http://www.linkedin.com/in/vitorbaptista>|
@vitorbaptista <http://twitter.com/vitorbaptista>

The Open Knowledge Foundation <http://okfn.org>

*Empowering through Open Knowledge*

http://okfn.org/  |  @okfn <http://twitter.com/okfn>  |  OKF on
Facebook<https://www.facebook.com/OKFNetwork> |
Blog <http://blog.okfn.org/>  |  Newsletter<http://okfn.org/about/newsletter/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20131119/773d5e08/attachment-0003.html>