There are some cases when we need to translate an entity not FROM the source languge, but TO the source language.
For example, a website content editor needs to create a page on the website in French (only in French), but the content editor knows only English and doesn't know French at all!
So, the right workflow for this is like this:
1. Create a page in French in the draft status, and keep the content empty.
2. Create an English translation of this page, in draft too.
3. Put the desired text in English to the English translation, and save it.
4. Use an external TMS or AI to translate this page from English to French.
5. Publish the French translation to make it available for site visitors. But keep the English translation in draft for future updates.
And this workflow doesn't work, because TMGMT doesn't allow to request a translation TO the source language: in that case, FROM English to French - the checkbox is simply disabled.
A workaround for this is to create the page in English, then translate it to French. But the issue here is that the default language for this page will stay as English, and Drupal provides no ways to change the default language of the entity!
This workaround leads to the issue that non-translatable fields are not available in the French edit form, and content editors have to edit them in the English edit form, separately from the translatable fields in French. Also, having the default language as English for a page, that is intended to be available only is French for users, leads to other issues with displaying, searching and filtering.
An easy solution for this issue can be just enabling translation TO the Source (Original) language, and allowing users to choose the source language manually.
So, just remove the "disabled" status for the Source (Original language) row in the table, and unlock the dropdown mode for the "Source language" section of the job creation form.
We will try to prepare a patch that implements this feature.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
murzComment #5
eugene_bsk commentedI have added changes.
Added the "Allow translation to the source language" setting, which allows allow creating translation jobs where the target language is the same as the source language and allows to select the source language on the job creation page.
Comment #6
murzComment #7
murzReviewed and tested, works well, and unlocks translating to the source language, to cover that use case! So, marking as RTBC.