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.
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
Translation provider settings
Translation provider
Batch task
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]
