Imroving translations via https://github.com/Gnucash/gnucash-htdocs/pull

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Imroving translations via https://github.com/Gnucash/gnucash-htdocs/pull

Frank H. Ellenberger-3
Hi all,

I just watched merging PRs is not sufficient to make the improvement
visible, because 'make mos' or 'msgmerge po/LL.po po/gnucash-htdocs.pot
-o po/LL.po' is not triggered.

Should we
* ask the committers to include the .mo file, having some binary
overhead in each commit,

* write a reminder (where) for core devs,

* something else?

Regards
Frank
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Imroving translations via https://github.com/Gnucash/gnucash-htdocs/pull

John Ralls

> On May 8, 2017, at 1:55 PM, Frank H. Ellenberger <[hidden email]> wrote:
>
> Hi all,
>
> I just watched merging PRs is not sufficient to make the improvement
> visible, because 'make mos' or 'msgmerge po/LL.po po/gnucash-htdocs.pot
> -o po/LL.po' is not triggered.
>
> Should we
> * ask the committers to include the .mo file, having some binary
> overhead in each commit,
>
> * write a reminder (where) for core devs,
>
> * something else?

No, pull requestors shouldn't be providing compiled catalogs. That would introduce an enormous security hole.

The best solution would be to fire off 'make translations' or some such with a receive hook on code that runs before the updated pages are pushed to Linas.

Regards,
John Ralls

_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Loading...