Contributors mailing list archives

Browse archives


Re: Translations and UI

Sunflower IT, Tom Blauwendraat
- 07/09/2021 12:50:35

My idea:

1. Write a one-time script that will replace all current source values for translated fields for records that are noupdate=1 or dont come from the database at all, with the French translation (gets rid of all the "copy names" and replace by something meaningful)

2. Add "en_GB" for English and dont use "en_US"

3. For any translated fields in future dont allow direct edit but force the user to use OCA "web_translate_dialog", which shows the source and all the translations in view so people will have to fill something meaningful always. We have made a module for this 'web_widget_enforce_translate', can opensource it when useful (wanted to, but didnt get the time to polish it)

On 9/7/21 10:22 AM, Rémi CAZENAVE - Le Filament wrote:

Dear all,

We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).

Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.

Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.

Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...

I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.

I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.

I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.

We will probably override write() actions to force lang in context.

I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !

Best Regards,


Le Filament

Post to: