Translation with glossary and target "EN-GB" gives error

[tgaertner]

Bad request. Reason: No dictionary found for language pair de-en-GB in glossary

Using "EN" as target language is deprecated. It also seems that creating glossary for "EN-GB" is not supported as well.

So whats the problem here or how can I work around this problem?

[JanEbbing]

Glossaries are not aware of language variants (en-GB, en-US, ...), they just use base languages (en). You can however use a glossary for a translation into any variant.

So as target language for your translation, you would need to choose en-GB, and as the glossary you need to use de to en.
See also the docs for this.

[tgaertner]

Thanks for the quick reply. This is exactly what I'm doing.

PHP:

$this->translator->translateText($text, 'de', 'en-GB', [TranslateTextOptions::GLOSSARY => $glossaryID]

Error:
Bad request. Reason: No dictionary found for language pair de-en-GB in glossary

[JanEbbing]

@tgaertner Are you sure you have a dictionary for de to en in the glossary you are using?

This test covers the case you are describing. IMO the error message is not ideal however, it should be No dictionary found for language pair de-en in glossary, investigating...

You can display the glossary with this endpoint/the getMultilingualGlossary method

[tgaertner]

Indeed I don't have one. So I need to check first if the glossary "supports" the language combination...?

[JanEbbing]

$this->translator->getGlossaryLanguages();

This method returns all language pairs we allow you to create glossaries in.
When you make a translation request with a glossary like $this->translator->translateText($text, 'de', 'en-GB', [TranslateTextOptions::GLOSSARY => $glossaryID]);, we require that your glossary actually contains a dictionary for the language pair you are trying to use. If you dont have terms for that language pair, you can simply translate without the glossary $this->translator->translateText($text, 'de', 'en-GB');. If you have a list of terms you want in the glossary, but haven't created the appropriate dictionary yet, you can add them via $this->translator->updateMultilingualGlossary().

We might add a non-strict glossary mode in the future, that allows you to pass a glossary ID, but only applies the glossary if there are applicable entries for this translation. As companies use glossaries to ensure e.g. brand identity, we err on the side of caution here and deny the request if an unsuitable glossary is passed with a translate request.

[tgaertner]

Ok, thanks. GOing to check for the language pairs first and then do the call without a glossary. in case there is none found.