[BUG] No difference in DeepL localization modes (autodetect)

[sebkln]

Describe the bug
There currently seems to be no difference in handling or behavior between the two localization modes "Translate with DeepL" and "Translate with DeepL (autodetect)", which are available in the localization modal.

• If no translated content exists on a page, the default language is used as the source language
• If another translation already exists, this language can be selected as the source language in an additional step inside the modal

I suspect that the additional step to select the source language was omitted for the "autodetect" mode in previous versions of this extension.

To Reproduce

1. Add two page translation to a page
2. Compare the two "DeepL" localization modes while translating page content to the first target language (no selection of source language available)
3. Compare the two "DeepL" localization modes while translating page content to the second target language (additional step to select source language available in both modes)

Expected behavior
The "autodetect" should skip the additional step and automatically use the default language of the site as source, if this was the originally intended behavior.
Otherwise, the "autodetect" mode should be removed.

Screenshots
This step in the localization modal is rendered for both modes, if at least one translation already exists on a page:

[calien666]

Hi @sebkln

You are absolutely right, we currently always use the language configured and there is no "autodetect" in real. This is mostly related to the glossary, which can't work without proper source and target languages.

We are aware of the autodetect currently not working as expected and the decision is outstanding, if this option should be removed or reimplemented. Currently, the state goes to "drop", as we implemented an auto-language detection on the places, where no source language is provided or not DeepL API compliant.