Problem

In the InstantTranslate text field the user can select from many languages, if for example a term collection is available for him which contains at least one term translated into many languages. This is very misleading, as the selection of let's say RU to FR may be available from the dropdpwn, but in fact no MT/LLM resource is available for that language direction and this will lead to an error message "no resource available".

Solution

Only show languages in the language dropdown for source or target that do have an LLM/MT resource available.
If either source or target is selected, the other dropdown should be filtered. E.g. user has MT resource DE- RU and FR - ES. When source DE is selected, target language ES should not be shown (or not selectable), or if target language is selected first e.g. RU, then as source language only DE is available for our example.

Sub-language logic

If resources are created with sub-language and sub-languages are enabled for the instance, the sub-language is shown and selectable following the logic described above, which is: when a machine resource is available. However, some services such as DeepL do not allow sub languages in every context. And if there are both available, sub-languages and generic languages we need to keep our logic:

Example:

Resources available for user are:

DeepL DE - EN-GB

DeepL DE - EN-US

DeepL EN - DE-DE

DeepL EN - DE-CH

GPT DE-DE - EN-GB

GPT DE-DE - EN-US

GPT DE-DE - FR-FR

Available source languages:

• DE
• EN
• DE-DE

Available target languages: for

• DE: EN-GB, EN-US, FR-FR
• EN: DE-DE, DE-CH
• DE-DE: EN-GB, EN-US, FR-FR