Elisabetta Masini 

Yes.  We have now prioritised this work and will doing it in the near future for both the plugin and the add-on.  No timescales yet, but yif you have the plugin installed you'll see the update in the notifications of Studio when it's available.

Awesome - thanks for the quick update. Loioking forward to it!

Elisabetta Masini 

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 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?

Thank you Paul ! I did not know about this. It sounds unnecessary complicated. I know we have 2 separate subscriptions (DeepL API and DeepL Pro) for 2 different reasons and needs we have. I have a question out about what API subscription we have and it looks like we may need to go for the API for business one BUT I'm not clear whether we actually need that one if we just want to be able to upload and use our own glossaries (not API created) when pre-translating via DeepL Pro in Studio.  We actually need to be able to use glossaries via API and via Studio. Does that mean that we need DeepL Pro AND DeepL API for business? Thanks!

Elisabetta Masini 

I think this bit is another very confusing part for users:

Elisabetta Masini said:

BUT I'm not clear whether we actually need that one if we just want to be able to upload and use our own glossaries (not API created) when pre-translating via DeepL Pro in Studio.  We actually need to be able to use glossaries via API and via Studio. Does that mean that we need DeepL Pro AND DeepL API for business?

DeepL has two types of glossary.  In the API documentation it says this:

"Glossaries created via the DeepL API are distinct from glossaries created via the DeepL website and DeepL apps. This means API glossaries cannot be used on the website and vice versa."

So if you are creating glossaries already without the API then you have created glossaries that cannot be used in Trados Studio (or any CAT tool).  The only way to get these glossaries into Trados Studio is via the API with an import feature.  So you would need both... I think.

I have to say the plans are not very clear.  There is an assumption that you need DeepL for Business because of the following:

1. you must have a DeepL API
2. two of the three API account specifically exclude CAT tool integration
3. if you can do it with an API account then this only leaves one and it doesn't specifically exclude CAT tools
4. Business includes everything in API Pro and this seems to only use glossaries created by API

Therefore logic tells me you need both.  But you should probably check with DeepL.

I also asked DeepL about any future plans to support one glossary for both needs and the response was this:

"Currently it is not in foreseeable planning whether we will merge the glossary endpoints in the future."

So it seems as though a long term workaround is in order or some development work on your end to help with the synchronisation of the two types.

Hi, I was wondering whether there was any news on this interesting topic.

Also I wanted to suggest the possibility of having Studio automatically insert Multiterm term translations through replacement in the MT segment translation as returned from the DeepL API. This would eliminate the need to make DeepL glossaries in the first place. But maybe I am 'hallucinating' .

Thanks

Hugo

Hugo Zwaenepoel 

Glossaries are available in the current version of the plugin.  We did update most of the posts discussing this but must have missed this one!

Hugo Zwaenepoel said:

Also I wanted to suggest the possibility of having Studio automatically insert Multiterm term translations through replacement in the MT segment translation as returned from the DeepL API. This would eliminate the need to make DeepL glossaries in the first place. But maybe I am 'hallucinating' .

The Deepl glossaries are apparently smart when it comes to dictionaries and will make sure the correct grammatical use of the terms is used.  A simple replacement of multiterm would not do that.  Certainly it's all possible, and how well we do it is also possible, but all with work and all at a cost... to us with our dev resources and probably to you with additional cost for whatever AI solution we use to support this in a smarter way.

No time period in sight... but definitely something we'll do at some point.  Or any developer could also look at this too... the APIs are all there!