Studio 2021 + DeepL - Error

Question

Hi all, A colleague of mine installed Studio 2021 and wanted to add the DeepL plugin. Her Studio version is 16.0.1.2917, and we just downloaded and installed the current plugin (version 5.8.17.1). The error message is: Fullscreen sdlerror-202097-9h41m40s.sdlerror.xml Download Der Wert darf nicht NULL sein. Parametername: source System.ArgumentNullException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 source System.Core -2147467261 SDL Trados Studio Studio16 16.0.1.2917 Microsoft Windows 10 Home NULL 1031 1252 BüroPC\Elke 4.0.30319.42000 BÜROPC True 8277272 MB What could be wrong here? Thanks for any help! Best Annette (from Manfred's account)

Paul · Accepted Answer

Thilo Pawelka Paul Tudoran Gilles DONATI Manfred Altmann Jens Olaf Koch Hans Widemann 
 We have released an update for 2019 and 2021 which is available on the appstore and via the 2021 appstore integration. This should solve the problems reported. 
 Thilo Pawelka said: I hope DeepL will make v2 available for CAT tool users so you don't have to update the plugin every time they come out with a new language variant. 
 In fact we managed to do this without using the endpoint they provided :-)

Paul · Answer

Gilles DONATI 
 Thanks for your investigation. I actually believe the problem is related to the API key provided by DeepL not supporting the use of the languages endpoint provided by DeepL in their AP documentation. The last update we released, among other things, changed the way we get the languages to avoid having to release new versions every time DeepL add a new language which is better for you, and for us. They provided an endpoint we can use for this and it works with the API key they provided to us for developing the plugin. 
 However, this morning (out of desperation because we could not reproduce this problem you are all having at all) I purchased a Pro subscription with DeepL so I went through the same process as you do. With my new API key the integration fails and I get the same error as you. 
 So, good that we now know where the problem is coming from. We have reported this to DeepL and are awaiting their response. I'm hopeful they will be able to resolve this at their end by allowing the keys to access the same endpoints available in their API. If they can't then we will change the plugin again and release a new version. We don't want to roll back because there are other important changes in this release that are needed by some users.

Paul · Answer

Jens Olaf Koch , Paul Tudoran , Gilles DONATI , Manfred Altmann , Hans Widemann , Thilo Pawelka 
 An update. We now know what the problem is, so here's a little history of how we got there so you will understand why we will have to undo some things we added and won't be able to achieve some things you have asked for in the past until DeepL make some changes: 
 
 Because DeepL are quite active and add new languages from time to time we used this feature in the last update to dynamically get the languages in the supported list: https://www.deepl.com/docs-api/other-functions/listing-supported-languages/ That recommendation came from DeepL 
 The API call here is this: https://api.deepl.com/v2/languages Note that it is v2 . 
 This morning DeepL pointed out for me that v2 is actually not available for CAT tools: https://www.deepl.com/docs-api/accessing-the-api/api-versions/ 
 So it seems that it's possible for them to generate different API keys depending on which API will be used v1, or v2. The API key DeepL provided us with for developing this plugin supports both v1 and v2. The API key they provide users with who purchase the professional subscription only supports v1. 
 The effect being everyone has a problem apart from us... the developers ;-) 
 
 As a result of this, we will undo some of the changes and go back to a hard coded language support using only v1. of their API. This will be done next week and we'll release an update as soon as possible.

Paul · Answer

Manfred Altmann 
 Interestingly Thilo Pawelka just reported the same error in another thread for 2019. For your user, who just installed 2021 I would guess the problem is related to there being no language pairs available in Studio yet (and we need to fix this if it's the case), but I didn't think that would be the problem for Thilo as he's an existing 2019 user. 
 Please try adding your language pairs here (if there aren't any) and then try again:

RWS AppStore > 2. RWS AppStore Applications

Studio 2021 + DeepL - Error

Top Replies