Translate
Deepl has recently introduced the capability to use a custom glossary when translating online.
Are there any plans to update the Deepl plugin so that we can take advantage of this feature?
Walter
RWS Community
Deepl has recently introduced the capability to use a custom glossary when translating online.
Are there any plans to update the Deepl plugin so that we can take advantage of this feature?
Walter
This has been discussed multiple times in the forum, you probably missed it :-) Yes, we do plan to address this. But the priority has been lower than other work e have had to deal with recently.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul ,
you've probably been confronted with this question way too many times, so sorry for asking it again: Will the Deepl glossary support be added by the end of this year?
Thanks in advance for your feedback!
KR,
Julian
Will the Deepl glossary support be added by the end of this year?
Maybe... we have been dealing with a lot of change, technically and resource wise, so we are only just getting back up to strength this month. All being well I hope we can get to this, but I can't say for certain.
I find it interesting there has been zero interest from any 3rd party developers to add this. We do open source the code.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
We would also be very keen for this function to be added to the plugin.
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:
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?
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul
Thanks for your feedback! Hm, this is rather confusing, as I can't find any obvious statement on the DeepL website regarding this limitation. I am well aware of the fact that the DeepL API licenses are not meant to be used with CAT tools (or, to put it differently, do not even work with them), but excluding the glossary feature from workflows where they are needed the most (for the translators, who definitely won't opt for an API license) does not make any sense to me. I am somewhat surprised that this hasn't been communicated more openly, as some CAT tools (memoQ, Transit) already have the glossary interface fully implemented, which requires users to enter a valid DeepL Pro Advanced or Ultimate key for the glossary feature to work.
So, in a nutshell, I am clearly left confused by this e-mail and looking forward to further insights from you as the investigation with DeepL is progressing.
Thanks in advance!
KR,
Julian
So, in a nutshell, I am clearly left confused by this e-mail and looking forward to further insights from you as the investigation with DeepL is progressing.
Yes... I was also very confused! I think I'm clear now anyway so documented our understanding in the wiki for the app: DeepL Translation Provider
We are working on the glossary support anyway and will release for the plugin and the add-on in due course.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
Thanks for the update! That wiki article does not mention the licensing issue, but I assume that - based on the other community discussions related to this topic - the glossary API used for the DeepL Pro CAT tool plug-in must be somewhat different from the one used with the DeepL web interface or accessed via other (desktop) applications. Hence, using an Advanced or Ultimate subscription to create DeepL glossaries via the DeepL plug-in should not get you into trouble...
That wiki article does not mention the licensing issue
Isn't it this part?
I clarified it but didn't make any comment regarding the penalties from DeepL for non-compliance.
the glossary API used for the DeepL Pro CAT tool plug-in must be somewhat different from the one used with the DeepL web interface or accessed via other (desktop) applications.
Correct.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
Sometimes clearing the cache of your browser does help - I'd missed the part regarding the supported licenses... Thanks for the clarification!