DeepL added glossary support in their API sometimes in the last year or so. See https://www.deepl.com/docs-api/managing-glossaries/.
When could we expect the plugin to support that option, including the ability to manage the upload/download/deletion of glossaries since they are different from the one used in the Web page.
Thanks.
As I’ve mentioned many times in this forum. We opensourced the code for the DeepL plugin and so any developer could do this.
But seeing as nobody else seems interested in doing it we’ll probably pick this up some time after the next release of Tradon Studio 2022 is out. We simply don’t have the available resource to look at this until then.
Not everyone out there is a developer who knows how to code a Trados plugin, so it's not that we are not interested in doing it, it's that we are not professional software developers, and need to spend more of our time on the language side of things than the coding side of things. I can read an API documentation, but it doesnt mean I know how to code this.
This said, I can understand the resource limitation. There is just an expectation that SDL will pick up that work when the last plugin version is "By Trados AppStore Team" , but maybe that doesnt necessarily mean it was done by SDL??
My post was merely to remind whoever is willing to update that plugin that the feature existed in API now, as it wasnt the case last year if my memory is correct.
Of course. Although I personally emailed over two thousand users who claim to be developed this week with details of how to upgrade their plugins for Trados Studio 2022, so there must be at least a few out there!
I wasn't picking on you though Michel. The functionality is there, and we would have liked to have done this already but things just get in the way. We have so many plugins that we are responsible for now that maintaining them all means we can't do things from one day to the next as we could in the "old" days.
There is just an expectation that SDL will pick up that work when the last plugin version is "By Trados AppStore Team" , but maybe that doesnt necessarily mean it was done by SDL??
Yes, it was done by the Trados AppStore Team... who are RWS. SDL is no more!
Thank you Paul. I am looking forward to when the RWS team has the time to work on this. Let's make sure the sentiment analysis parser of this forum agrees that we ended this discussion on a positive note!
We do have a dev Team in our company that can help with tooling for translation. They are very busy with many other things we ask them to do for us, but I will get their opinion on how hard it is to work on one of these plugins on GitHub. There is another plugin we are really trying to make work for us, it's the GoogleCloud_n_Glossary for Studio 2019, but that one is not opensource and we are trying to see with the developer why it's not working for us (it forgets its credential every time you reopen the project or start from a template). In the end, we may end up coding this ourselves or asking someone to do that for us. Perhaps there is a way to start from the latest MT Enhanced Plugin for Studio 2021 and see if we could down port it to support Studio 2019, which is the version we must use. I know that one is open sourced. Do you, by any chance, know why the support for the Google Advanced API (v3) was not brought to the plugin version for Studio 2019? Was there a technical limitation?
Let's make sure the sentiment analysis parser of this forum agrees that we ended this discussion on a positive note!
An excellent idea :-)
Do you, by any chance, know why the support for the Google Advanced API (v3) was not brought to the plugin version for Studio 2019? Was there a technical limitation?
From memory I believe we used libraries that were introduced in 2021 and that was the main reason we decided not to maintain it for 2019 as well. You could still use the base code but would probably have to rewrite parts of it so it was supported properly in 2019. Given we are moving to 2022 shortly we'll be focusing on ensuring support for 2021 and 2022.
Hi Paul, I just stumbled across this post, thanks for giving an update on how the development of the DeepL plugin is going.
Regarding the "any developer could do this" part: I'm not a developer, but maybe I can forward this task to one of our developers (although, just like you, they are permanently more than busy).
Is this the place where a developer would find the code for the current plugin and also all the necessary information on how to update it?
https://github.com/RWS/Sdl-Community/tree/master/DeepLMTProvider
Or is there any additional information/documentation a developer would need (and not find by himself)?
Maybe I can convince comeone to get his hands on this.
Although we do plan to pick this up I'd really love to see external developers contributing to the source code we provide. So yes, that link is where you'll find the code. You'll also find all the API documentation across all of our products here:
And more specifically for Trados Studio here:
https://developers.rws.com/studio-api-docs/index.html
We version control the API documentation now so you'll see the 2022 Beta is the default. Shortly this won't be Beta anymore, but you can still see the older versions down to 2019 if you need them. We only support two major versions back and we didn't have all the resources automated in the way they are now for earlier versions, but hopefully what's there will enough for most developers.
Thanks a lot, Paul!
I will adress this internally and keep you posted.
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:
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.
Translate
