FR: Support for glossaries with the DeepL API?

[mersy]

Will you support glossaries with the DeepL API?

https://developers.deepl.com/docs/api-reference/glossaries

[JodebaDigitalPulse]

hi @mersy,

I did not know this feature yet.

I guess you want to enable the usage of your existing glossaries when translating in the CMS. Do you think we can achieve this with a new setting to select all the glossaries you want to enable? So they will always be used for each translation.

Managing the glossaries may be too far out of scope for this plugin.

[mersy]

Hi, @JodebaDigitalPulse

Thank you for your comment.

Managing the glossaries may be too far out of scope for this plugin.

Yes, I feel that managing glossaries will need to be done using the DeepL API in a different way, not through Multi Translator plugin. For example, managing the glossaries as Craft CMS data and using the DeepL API to handle the glossaries by custom plugin.

---

Since this is also my first time researching this, I don't have a complete understanding of everything.

When you specify a glossary_id during translation,it seems that terms from the glossary are prioritized.

https://developers.deepl.com/docs/api-reference/translate

However, it appears that the glossary_id is updated each time the glossary is updated, so I think this needs to be considered.

• Retrieve the glossary_id based on the name of the glossary
• Use that glossary_id during translation

This might be the approach to take.

So, there seem to be the following patterns:

• Save the name of the glossary in the Multi Translator plugin settings, retrieve the glossary_id using the DeepL API, and then translate
• Save the glossary_id in the Multi Translator plugin settings and use it for translation

Saving the name of the glossary seems to be better for user. However, it seems that there might be many patterns, or even multiple patterns, for the combination of source_lang and target_lang, so it seems difficult to determine the best way to save the settings.

[JodebaDigitalPulse]

Thank you, I'll have a look at it, and discuss it with the team. I'll keep you updated. 👍

[mersy]

Thank you!!

[JodebaDigitalPulse]

Hi @mersy,

update the plugin to the latest version (there will be a migration to run as well) and you can test this new feature: https://github.com/digitalpulsebe/craft-multi-translator?tab=readme-ov-file#manage-glossaries

Let me know what you think.

Kind regards, Jonathan

[mersy]

Hi, @JodebaDigitalPulse

Sounds great!!

I'll try it later.

Thanks mersy

[mersy]

Hi, @JodebaDigitalPulse

I updated the plugin and tried out the glossary feature. I was able to confirm that the terms specified in the glossary are being used in the translation.

It's great! Thank you very much!

[JodebaDigitalPulse]

Good, thank you for testing! 😊