DeepL - means to mark certain words "do not translate"?

[Dave Gehman]

We have a product that uses common words (design, parent, child, and more) in an idiosyncratic way. In addition, we supply many hundreds of pre-built objects whose names have to be entered in their English form when typed into text forms and formulae (e.g., BaseAssembly, ModelDeleteButton... many many more).

Online, DeepL provides a way to enter what they call "customizations," where we can essentially provide our glossary and those words are then not translated. To be precise, they couch this as translation pairs. We enter those as, for example "Model" > "Model", "Child" > "Child", etc.)

Is there a way to provide a "do not translate" glossary when DeepL translating from within H+M?

[Tim Green]

Hi Dave,

This isn't supported at the moment but it is one of the things we are looking into for future updates.

[Dave Gehman]

... it is one of the things we are looking into for future updates.

[patiently waiting at the bus stop... looking at my watch... hoping it gets here soon...]

Thanks, Tim
Dave

[Alexander Halser]

This has been implemented in build 5600.

A pre-release version is available from this link:
https://www.helpandmanual.com/download/ ... p-v811.exe

The DeepL plugin now respects protected (= non translatable) text. Please note that there might occur some glitches like spaces vanishing after a protected word. You can see this in the screenshot below. That's a DeepL bug and they told us today, that they are working on it.

[Dave Gehman]

Thanks - an extremely useful addition to an extremely useful add-on!