Is your feature request related to a problem?
It is related to the problem that the modifications of language data is lost between the time a PR is created and merged when migrating modules to a new version.
Describe the solution you'd like
Install the weblate auto translation add on. And give OCA-bot and weblate users the possibility to use this function.
(Does a new permission group needs to be created so only selected weblate users with enough experience can use this function? \ maintainers?)
Triggers can be used to auto translate addons.
Use case 1:
When a PR is merged which contained an old snapshot of the translation files.
Weblate can be triggered by a bot to preform an auto translate with the previous major odoo version language files as input and forward port it to the migrated branch.
Use case 2:
The language data of an older branch e.g. V8 contains more info then the recent branch.
An automated translate can be triggered to forward port the translation data to for example branch V14.
Thus it is used as a corrective maintenance tool. (until weblate infrastructure is optimized to auto forward port translations)
Use case 3:
Auto translate common words between oca branches to improve consistency.
(Example The same word can have an different translation in the \project branch then in the \edi branch)
While presenting them in the same ERP gui, it comes across as sloppy.
Can also be used for manual administration tasks (aka forward porting translations.)
Is your feature request related to a problem? It is related to the problem that the modifications of language data is lost between the time a PR is created and merged when migrating modules to a new version.
Describe the solution you'd like Install the weblate auto translation add on. And give OCA-bot and weblate users the possibility to use this function. (Does a new permission group needs to be created so only selected weblate users with enough experience can use this function? \ maintainers?)
Triggers can be used to auto translate addons. Use case 1: When a PR is merged which contained an old snapshot of the translation files. Weblate can be triggered by a bot to preform an auto translate with the previous major odoo version language files as input and forward port it to the migrated branch.
Use case 2: The language data of an older branch e.g. V8 contains more info then the recent branch. An automated translate can be triggered to forward port the translation data to for example branch V14. Thus it is used as a corrective maintenance tool. (until weblate infrastructure is optimized to auto forward port translations)
Use case 3: Auto translate common words between oca branches to improve consistency. (Example The same word can have an different translation in the \project branch then in the \edi branch) While presenting them in the same ERP gui, it comes across as sloppy.
Can also be used for manual administration tasks (aka forward porting translations.)
https://docs.weblate.org/en/latest/admin/addons.html#addon-weblate-autotranslate-autotranslate
https://docs.weblate.org/en/latest/user/translating.html#auto-translation