targetLang="en" is deprecated, please use "en-GB" or "en-US" instead

[deeplcom]

targetLang="en" is deprecated, please use "en-GB" or "en-US" instead

[JanEbbing]

Hi, what is the bug here exactly? The information is in the readme:

Some target languages also include the regional variant according to ISO 3166-1, for example 'en-US', or 'pt-BR'. The source language also accepts null, to enable auto-detection of the source language.

and this is not a recent change, we haven't accepted en as a target language for years.

You can use Translator::getSourceLanguages() and Translator::getTargetLanguages() to query the currently accepted languages from the API, or use the constants we define in the library, note the comments for english:

    /** English language code, may only be used as a source language. */
    public const ENGLISH = 'en';

    /** British English language code, may only be used as a target language. */
    public const ENGLISH_BRITISH = 'en-GB';

    /** American English language code, may only be used as a target language. */
    public const ENGLISH_AMERICAN = 'en-US';

[kalebheitzman]

@JanEbbing that's weird. Our plugin was working fine when using just en as a target language code and it just broke in the last few weeks with that deprecation notice. The documentation states that you have to pass a locale code in order for the glossary to work and unless we change our Moodle install to use regional variants we'll have to hardcode locales into the plugin to make it work with DeepL now.

On the readme it shows $translationResult = $translator->translateText('Hello, world!', 'en', 'fr'); but my understanding is that I now have to use en-US or en-GB, etc and that I cannot use en. Am I misunderstanding something here?

[JanEbbing]

Hi @kalebheitzman - not sure why it broke, but we did not change anything in this regard. DeepL differentiates between a sourceLanguage (language the text is in, can be null in order to be inferred) and a targetLanguage (language to translate the text into) - the targetLanguage needs the regional variant to be specified, else it will throw an error (unfortunately only once you actually call the function, as we want users of older library versions to be able to use languages released after the library version).

In the example

$translationResult = $translator->translateText('Hello, world!', 'en', 'fr');

we call translate with a sourceLanguage of 'en' and a targetLanguage of 'fr', which is fine. On the other hand,

$translationResult = $translator->translateText('Bonjour, le monde!', 'fr', 'en');

would throw an error, you would need to write something like

$translationResult = $translator->translateText('Bonjour, le monde!', 'fr', 'en-GB');