Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
When working with language resources the mapping between the languages of the language resource and the languages in translate5 was improved, especially in matching sub-languages. For Details see the issue.
-
Empty show more show less
Description
Selectable language resources in task association
- If the task language is a sub-language (e.g. de-CH):
- language resources that belong to the same sub-language should be selectable (e.g. de-CH, but not de-DE)
- language resources that belong to the same major language should be selecttable (e. g. "de")
- if the task language is a major language (e. g. "de")
- all language resources that belong to sub-languages should be selectable (e.g. "de-DE" and "de-CH" and "de-AT")
- language resources that belong to the same major language should be selectable (e.g. "de")
Selectable languages for language resource creation
- If a language resource supports all languages, that translate5 supports, all languages should be selectable
- if a language resource (as it is the case with all MT resources) only provide some languages or sub-languages, only the supported languages should be selectable. This is also true for sub-languages: If a not supported language is selected, on saving the language resource the server-side should send an error to the front-end that should mark the corresponding language field in the dialogue as wrong (red border and corresponding message). This is also true for sub-languages. For example DeepL does not support de-DE or de-CH as sub-languages for German, therefore they should be marked as wrong, if they are selected for DeepL
Languages that are send to a language resource, when querying it for matches
Currently it looks like translate5 sends the language of the task to a language resource, when it queries for matches.
Instead the language of the assigned language resource must be send. Otherwise it leads to errors, for example if the language of the task is "de-CH", but the language of the assigned DeepL resource is "de", because DeepL does not support "de-CH".
Please check this for all integrated language resources.
Queried language resources in InstantTranslate
The logic is analogous to the selectable language resources for the task association:
- If the selected language in InstantTranslate is a sub-language (e.g. de-CH):
- language resources that belong to the same sub-language should be queried (e.g. de-CH, but not de-DE)
- language resources that belong to the same major language should be queried (e. g. "de")
- if the task language is a major language (e. g. "de")
- all language resources that belong to sub-languages should be queried (e.g. "de-DE" and "de-CH" and "de-AT")
- language resources that belong to the same major language should be queried (e.g. "de")