Glossary Terms Overridden When Using DeepL Plugin in Trados

Question

We use the DeepL plugin for machine translation (MT) in Trados, combined with custom glossaries. However, we've noticed that glossary terms are occasionally overridden when translating in Trados, something that doesn't happen when using DeepL directly in the browser. 
 This issue has consistently occurred when translating into English, with the target language set to EN-GB. Our glossary uses Oxford spelling, so terms like characterized (with a "z") are intentionally included. The problem is that these terms are being "corrected" in the output to use an "s" instead, such as characterised , despite the glossary specifying the "z" spelling. 
 
 How can we solve this? Has anyone encountered a similar problem? What could cause this to happen? Thank you in advance. 
 Below a few screenshots of examples including the Task History in Trados.

Example glossary entries:

The output in Trados overruling the glossary when target language EN-GB is selected: 
 
 Same segment when target language EN-US is selected: 
 
 Glossary in Browser works just fine:

No hints to some kind of spelling correction by Trados in the Task History:

Handling of glossaries according to DeepL: 
 https://developers.deepl.com/api-reference/multilingual-glossaries#language-variants

Paul · Answer

Elisabeth Orion 
 Are you aware of the limitations here? 
 https://support.deepl.com/hc/en-us/articles/360021634540-About-the-glossary 
 
 Glossaries created via the DeepL website and DeepL desktop apps are different to the glossaries within your CAT tool. This means that these glossaries cannot be used within your CAT tool and vice versa. 
 
 Given your test comparison showed it working in the browser I suspect it's because you are using a glossary created in DeepL and not created via the Trados Studio DeepL plugin interface. Can you confirm that?

Paul · Answer

Elisabeth Orion 
 Thanks for that clarification. Shame such a process is needed, but I guess we need to wait for DeepL to support glossaries in a more effective manner. 
 In the meantime, you mention this is almost always used correctly, but sometimes it's not. That makes it tricky and I think the first thing you need to do is demonstrate where it's not working by sharing an example of something we can reproduce. So if you can provide the following small examples: 
 
 sample source file 
 sample csv 
 
 Then we can test this ourselves specifically. If it helps to reproduce the issue then a developer will almost certainly fix it. 
 You also seem technical given your reference to the API documentation so you might also be interested to look at the source code too as this is an open sourced application: https://github.com/RWS/Sdl-Community/tree/master/DeepL%20Translation%20Provider 
 The appstore team will welcome any pull requests from 3rd party developers who find a problem and fix it. Often a faster way since we only need to validate the code and publish the fix.

RWS AppStore > 2. RWS AppStore Applications

Glossary Terms Overridden When Using DeepL Plugin in Trados