Archives
Contributors
Re: 16.0 translations
the i18n_extra mechanism still works exactly as it used to.
That includes that translations are only overwritten on the first init of a
module, or with -u $module --i18n-overwrite.
--
Your partner for the hard Odoo problems
https://hunki-enterprises.com
by Holger Brunn - 11:41 - 20 Jun 2024
Reference
-
16.0 translations
Hi guys,
We do have a customer which would like to translate a term used in a python method in a odoo module.
I know translations have changed a lot in 16.0, that and now field translations are stored as jsonb values.
To give you more context, here's a bit of code https://github.com/odoo/odoo/blob/16.0/addons/l10n_din5008_sale/models/sale.py#L12-L32
Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.
In the previous versions of odoo, it was possible to create a `l10n_extra` folder, and drop a new translation for the term, and that's it.
Now it's not possible anymore, and I'm looking for ways of doing it.
For instance, if some python code is raising an exception with some translated text that you're unhappy with, you cannot change it.
I noticed there was a few issues on this matter on github.com/odoo/odoo- https://github.com/odoo/odoo/issues/157815
- https://github.com/odoo/odoo/issues/168098
- https://github.com/odoo/odoo/issues/164736
- https://github.com/odoo/odoo/issues/124124
- ...
I'm guessing that we aren't near close of having a solution from Odoo, and was wondering if there was anything in OCA about this?
Thanks!
---
Matthieu Méquignon
by Matthieu Méquignon - 04:04 - 20 Jun 2024