"Probability score": 0.6

"Question improvement suggestion": Please provide more details about the issue you're facing with the DeepL Plugin, including the version of Trados Studio you're using, the steps you've taken so far, and any error messages you've encountered. Also, please clarify what you mean by "Nex_gen API support".

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello,

Thank you for your suggestion to add English-Arabic glossary support to the DeepL Plugin. As of now, Trados Studio does not support the DeepL Glossary function. However, we do have plans to include this feature in the future.

Regarding your request for Nex_gen API support, could you please provide more details? This will help us understand your needs better and provide a more accurate response.

In the meantime, you might want to explore the Dictionaries feature in Language Weaver, which offers a similar function and is supported by Trados Studio.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

 Muhammad Khateeb 

Muhammad Khateeb said:

kindly add En-Ar glossary support in this Plugin

Ignore the Community AI response... we need to retrain that!  We do of course support glossaries, however the languages that are supported are not anything we have control over.  If you look at the API documentation for DeepL you will see that Arabic is not supported for Glossaries:

https://developers.deepl.com/docs/api-reference/glossaries/openapi-spec-for-glossary-management#glossary-language-pairs

Muhammad Khateeb said:

Add Nex_gen API support

Please elaborate on this point?  And also think about who you are directing the question to.  We are not DeepL, so all we do is provide a plugin that can use the features they make available through their API.  If you want enhancements to DeepL please contact them directly.

thank you Paul  for these clarifications:

kindly note this regarding Nex gen

https://developers.deepl.com/docs/resources/release-notes

https://developers.deepl.com/docs/api-reference/translate#about-the-model_type-parameter

Note that the quality_optimized value for the model_type parameter is currently supported only in the Pro v2 API (api.deepl.com/.../translate).

https://www.deepl.com/en/blog/next-gen-language-model

Thanks.

Muhammad Khateeb 

Thank you.  Did you also note the following:

• Arabic is not supported yet for Next Gen
• The /languages endpoint has not yet been updated to include information about model_type support

But we will keep an eye on it.

Yes, I noted

 Thank you for keeping an eye on it, and updating the DeepL plugin to catch all capabilities 

Paul 

I think the supported languages are updates now, kindly check it

Languages supported | DeepL API Documentation

 Muhammad Khateeb 

Thanks for pointing that out.

  Oana Nagy fyi.

I tested the API quickly and it looks like these are all supported now:

PDF