Michel Farhi-Chevillard Thilo Pawelka 

We have been discussing a few things with the DeepL team and I wanted to make sure you understood that this feature will not be available to you if you only have a Pro account?

It will only be available to users with a "DeepL API for Business" subscription.  This is because of what DeepL support, not because of anything we are restricting.

To quote the information we were provided with:

"However, in case of additional development to your plugin, it should be noted that customers with a DeepL Pro Advanced or Ultimate subscription (the prerequisites for CAT Tool integration) are not allowed to create the glossaries themselves via direct API request.
Direct access to our API by customers who do not have a DeepL API subscription counts as a violation of our Terms and Conditions and may result in a corresponding suspension for these customers."

So this means you have to have a DeepL API subscription of which they offer three types:

• DeepL API Free
• DeepL API Pro
• DeepL API for Business

Of these three only one includes CAT tool integration and that's "DeepL API for Business".

We are currently investigation with DeepL how we are able determine the style of subscription a user has as this is not clear.  But this is likely to be news for some users, possibly like you, who have a Pro subscription and believed this meant you can work with glossaries.

You should also be aware that there are glossaries, and there are glossaries!  The glossaries you create using the API are not the same as the glossaries you create manually.  So you will not be able to use the ones you created in your account as they cannot be accessed via the API... and vice versa.  This means a lot of synching between the two if you wish to keep them in synch... something you will have to do manually.

Also, the DeepL API does not support an ability to change a glossary.  So if you need to make changes you would have to delete the existing one and recreate a new one.

All in all possibly not a particularly attractive option.  I would be very interested to learn your view on this information if you were not aware of it already?

Hi Paul , 

Thanks for the information. Please talk to DeepL again, and ask them about customers who are grandfathered into plans which no longer exist. In our case, we have a "DeepL Pro Classic" plan from before the time when they separated API access from CAT tool access.  My account description on the web site clearly states that I can "Use within your CAT tool without limits" and "Access the DeepL API".  So, when RWS implements the glossary support and the check for subscription, I should be able to continue using my plan in Trados and use the glossary feature.

Michel Farhi-Chevillard 

I can ask... but we will only be able to work with the endpoints they provide.  I think in reality this may be something you have to take up with DeepL.  I can well imagine if they didn't have glossary support back then (and I suspect they didn't) that they have always excluded glossary support from the API whether you had a CAT tool integration or not once they introduced it.  At the moment we can't even see how to validate what kind of account a user has.  It all seems a little unclear.

But I will ask.

Thanks, please keep us informed.  At the very least, I do not want to lose my ability to use DeepL in Trados (without glossary) just because the DeepL Pro Classic plan is not recognized.  That would be a big step backwards. One reason we like DeepL over other engines is that it seems to handle tag placement better.   I don't know for sure if it's the engine, or the Trados plugin, but that's what we noticed. I have an unfinished discussion with Lydia Simplicio about this, but as of now, we are not able to get good tag placement with our AutoML engines. So, when we have a document with heavy tags, we prefer DeepL, even if that means using a generic engine (but hence the desire to couple that with glossary support).

Michel Farhi-Chevillard Thilo Pawelka 

I have tried to summarise the situation now after several conversations with DeepL and have put it into the wiki we have for the plugin here:  DeepL Translation Provider 

We have been working on the plugin anyway and will release an update to both the plugin (Trados Studio) and add-on (Language Cloud) in due course that provides glossary support.

On this:

Michel Farhi-Chevillard said:

we have a "DeepL Pro Classic" plan from before the time when they separated API access from CAT tool access. 

It was mentioned in the discussion and I believe it will be supported.  I don't think they like it because it potentially provides too much uncontrolled access so I wouldn't be surprised if if gets replaced with one of the more recent subscriptions in time.  But this is something for you to clarify with DeepL support.

Michel Farhi-Chevillard if you have Trados Studio SR1 installed, please download the latest version of DeepL (6.1.2.18) you will find Glossary Support. Light documentation on this topic can be found on the Wiki Page:  DeepL Translation Provider  

Michel Farhi-Chevillard if you have Trados Studio SR1 installed, please download the latest version of DeepL (6.1.2.18) you will find Glossary Support. Light documentation on this topic can be found on the Wiki Page:  DeepL Translation Provider