Are glossaries available for the DeepL integration?

Question

From what I can see, DeepL allows for glossaries to be used via its API. I can't see that being possible in the Trados Plugin, but I am wondering whether there are plans to make that feature available? It would add a lot of value. 
 https://www.deepl.com/de/docs-api/glossaries/ 
 Daniel

Paul · Accepted Answer

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.

Daniel Hug · Answer

Paul Wow. I was living in the past. Well, "Individuelle Preisgestaltung" means it's not affordable for small teams or individual users. It's a high threshold.

Paul · Answer

Yes, there are plans. But we have limited resource and this is further down our priorities list. I'm a bit disappointed nobody ever takes the open source code we provide and extends it for the greater good of all users... it would certainly make the experience of all users a much better and more dynamic one. 
 But in the unlikely event anyone ever does this we will get around to it when it reaches the top of our own list.

Paul · Answer

We actually had several thousand developers registered when we used to do this via the old appstore, not all were translators, but some were. There are quite a few notable translators developing today. I think my point was it would be great if we could build more of a contributory platform for plugins because everyone would benefit from this. Instead, what I see very often is developers taking the code we have opensourced and then using it for their own purposes within their own creations. I think this is also ok and it is indeed one of the reasons we opensource to help developers get a start in what they're doing... but I have always been disappointed at the lack of reciprocity for benefit of everyone. 
 Unknown said: Did you ever have a "beginner's code camp" or something? 
 In fact we did do this. When we first set up the appstore and started opensourcing code the first developer we had in our dedicated team at the time wrote a series of blog articles to help developers get started, and they are still available on his personal blog today: 
 https://romuluscrisan.com/openexchange-where-do-i-start/ 
 The reference to OpenExchange is what the AppStore used to be called... a name I wish we'd kept as I think this not only differentiated us from an "AppStore" that everyone has these days, but it also embraced the concept of being open which is a philosophy we still adhere to today. 
 In addition to this we also ran a series of open days around the world and I travelled with Romulus around Europe and Asia where we ran a day of training to help interested parties get started. Despite the effort we put into this, and the cost involved because we did not charge at all for his, I'd have to say that the events were not well attended. Also disappointing. I think part of the reason for this is the immaturity of this industry in recognising the benefits of having a developer and being able to build your own solutions around an established technology that will do the basics and allow you to build on whatever you want. Some companies definitely do take advantage of this and it's noticeable just how much they do as we see a lot of these efforts that never get published on the appstore. And I think these progressive companies learned how investing in even a single developer reaps massive rewards to help them step up against their competition and improve their overall localization processes. 
 We have spoken many times about how we might go about creating content to help more developers get started, but our experience of the past does make it hard to prioritise and definitely doesn't help us get any budget to do anything more than what we can manage to do ourselves, within our team, more based around the willingness and dedication of our team to give up their time to create it. Reading these forums it's always clear to me how much our teams are underestimated and how much their individual sacrifices to try and help goes completely unnoticed. No surprise there, but I am always surprised at how these guys continue to deliver despite the negativity we often see in here. 
 Apologies for the small rant, but what you are asking for is exactly what we put a lot of effort into in the past and got nowhere. However, I am always open to any suggestions we can incorporate alongside our own plans and maybe even find enough of a reason to prioritise them a bit more.

Paul · Answer

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?

Trados Studio > 4. Machine Translation

Are glossaries available for the DeepL integration?

Top Replies