Contributors mailing list archives


Re: Transiflex to OCA

Acsone SA/NV, Jonathan Nemry
- 15/07/2016 16:57:41
Thank you for your answer!

One more things: I just noticed that the en.po are generated too from transiflex. It is very problematic because it means that a modification into the source code for the value of the field name will not appears with a simple update of the module. Is there a way to delete this en.po from the i18n? Or a solution to block its generation from transiflex?

many thanks


2016-07-07 15:52 GMT+02:00 Maxime Chambreuil <>:
Hello Jonathan,

This script runs every week-end and pushes new translations to Github:


Ursa Information Systems Maxime Chambreuil
Project Manager / Consultant

Ursa Information Systems
1450 W Guadalupe Road, Suite 132
Gilbert, Arizona, 85233

Office:     1-855-URSA ERP x 710
                1-855-877 2377 x 710
Mobile:   1-602-427-5632

On Thu, Jul 7, 2016 at 6:53 AM, Nemry, Jonathan <> wrote:
Dear contributors,

I have a question about how exactly works transiflex with OCA.

Actually I translated some terms of OCA purchase-workflow on transiflex. So my question is to know how those translated terms will be pushed back into the purchase-workflow sources?

I've search documentation but didn't find anything.
If someone knows the correct workflow to update oca translations then please let me know it or let me know where it is documented.

Thank you all in advance!



Post to:

Post to:

Nemry Jonathan
Software Engineer

Tel : +352 20 21 10 20 23
Gsm : +352 691 506 013

Acsone SA, Succursale de Luxembourg
22, Zone industrielle
L-8287 Kehlen, Luxembourg