Pivot Language

[Ere-Eye]

Describe the problem

We mainly work with sources that are in Chinese Simplified which we translate into English first which we then use English as the source for other languages such as French, German, Russian, and etc. which is a very common strategy in the world of localization.

Describe the solution you would like

I would like to be able to set Chinese Simplified as the source for English translations and set English for the translations that come thereafter. If there happen to be changes in the English translation from the source material, then the other languages should be notified accordingly, especially for changes in glossaries.

Describe alternatives you have considered

I made it work somewhat with the "Quality gateway for the source strings" using the Intermediate language file issue here by creating a component with its source language set to English and using the original source as an intermediate language file so that each string's translation interface includes a section named " Intermediate language " showing the original. When making changes to already established strings in the English, the other languages do get marked as "Strings marked for edit". However, when working on the English translations, they are not recognized as such and Machine Translations become unavailable. They also come prefilled with the strings that are in the intermediate language file. So arguably the most important step for our process which is translating the pivot the language ends up with a few obstacles that effect efficiency and ease of use when using this bandaid solution.

Screenshots

Additional context

No response

[github-actions]

This issue has been added to the backlog. It is not scheduled on the Weblate roadmap, but it eventually might be implemented.

In case you need this feature soon, please consider helping or push it by funding the development.