When a user clicks "Translate" in the page module to create a new language version, they expect a translation (Source A -> Target B). The button "Optimize with DeepL Write" is currently listed alongside the translation options.
If a user selects this, the content is merely copied to the new language column without being translated, as DeepL Write is a monolingual editing tool. This causes confusion for editors who expect an automated translation.
Suggested Improvement:
Disable or hide the "Optimize with DeepL Write" button in the initial "Localize page" wizard if the target language differs from the source language.
When a user clicks "Translate" in the page module to create a new language version, they expect a translation (Source A -> Target B). The button "Optimize with DeepL Write" is currently listed alongside the translation options.
If a user selects this, the content is merely copied to the new language column without being translated, as DeepL Write is a monolingual editing tool. This causes confusion for editors who expect an automated translation.
Suggested Improvement:
Disable or hide the "Optimize with DeepL Write" button in the initial "Localize page" wizard if the target language differs from the source language.