Deepl plugin 6.2.3.1 - Trados Studio 2022 SR2 - Empty NMT segments when using glossaries

Software

Trados Studio 2022 SR2 - 17.2.11.19134

DeepL plugin: 6.2.3.1

DeepL subscription: DeepL Pro Advanced account

Glossaries

CSV files (with comma separator) are used to create the glossaries.

Add glossaries' details window with a glossary named 'EN-BG_euipo_official_termbase', source language set to 'en', target language set to 'bg', and delimiter as a comma.

Note: I have noticed that CSV files must be encoded using UTF-8 with BOM. If glossaries are created without BOM, any special characters appear corrupted.

This is not included in the documentation of the plugin in the App Store https://appstore.rws.com/Plugin/24?tab=documentation

The Trados projects used for testing are configured using EN-GB as source language and Bulgarian BG as one of the target languages. Other target EU languages are configured in the same project.

The same behaviour and issue occurs will all languages.

Question: I wonder if "en" is the correct source language code for EN-GB or EN-US.
Which language code is to be used for each of these language variants?

Situation

If the glossary is deactivated, the DeepL glossary works as usual and MT is applied to the segments in the SDLXLIFF file.

Issue

If the glossary is configured/activated in the projecft, the Pre-translate Files batch task including Apply MT gets completed, but the new segments remain empty without MT.

Glossary

Close-up of the 'Add glossaries' details' window showing the 'OK' button and the glossary 'EN-BG_euipo_official_termbase' with source 'en' and target 'bg'.

Translation provider settings

DeepL Translation Provider settings window showing an obscured API key, language pair 'en-GB' to 'bg-BG', formality set to 'Default', and glossary 'EN-BG_euipo_official_termbase'.

Translation provider

Translation provider list with 'DeepL Translation provider' selected, showing enabled status, languages as 'na', lookup penalty '0', and no concordance.

Batch task

Pre-Translate Settings window with options for translation overwrite mode, confirming matches, locking matches, and applying automated translation when no match found.

Does the plugin needs to be configured differently?
Is there something else I should do to apply DeepL MT with glossaries?
Otherswise, what could be the issue and how can it be resolved?



Generated Image Alt-Text
[edited by: RWS Community AI at 9:54 AM (GMT 0) on 13 Jan 2025]
emoji
  • "Probability score": 0.7

    "Question improvement suggestion": Please provide more information about the error messages you are receiving, if any. Also, it would be helpful to know if there have been any recent changes to your system or software.

    "In the meantime, based on the information you have provided, here is a suggested answer to your question:"

    Hello,

    From your description, it seems like you're having issues with the DeepL plugin when using glossaries in Trados Studio 2022 SR2.

    The language code for English (United Kingdom) is "en-GB" and for English (United States) is "en-US". These are the correct source language codes to use for these language variants.

    As for the issue with the glossary, it's possible that there might be a conflict between the glossary and the DeepL plugin. Here are some steps you can try:

    Step 1: Ensure that your CSV files are correctly formatted and encoded in UTF-8 with BOM. This is crucial for the correct display of special characters.

    Step 2: Check if the glossary is correctly configured in your project. Make sure that the terms in the glossary match exactly with the terms in your source text.

    Step 3: Try deactivating and reactivating the glossary to see if this resolves the issue.

    Step 4: If the issue persists, you might want to consider reinstalling the DeepL plugin or updating it to the latest version if an update is available.

    If none of these steps resolve the issue, it might be a bug with the DeepL plugin itself. In this case, you might want to reach out to the developers of the plugin for further assistance.

    I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

    RWS Community AI

    emoji
  • Note. The DeepL glossary functionality does not support BG.

    Supported languages

    https://support.deepl.com/hc/en-us/articles/360021634540-About-the-glossary

    I have the issue with supported languages such DA, NL, PL, PT, RO and SV.

    It is an ackward behaviour that the DeepL plugin allowed me to select glossaries for unsupported languages.

    I have restarted Trados Studio 2022 and now it seems to only display supported languages:

    Screenshot of the DeepL Glossaries interface with an 'Add glossaries' details' window open, showing a dropdown menu for selecting the target language with options like de, en, es, and others.

    I am going to resume the tests with the DeepL plugin ussing glossaries.

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 1:37 PM (GMT 0) on 13 Jan 2025]
  • I tried with 2 supported languages (DA and NL) and 40 files each time and MT is applied. To be checked if the terms from the glosssary are applied, but it seems to be working.

    emoji