Hello!

I've been evaluating DeepL in combination with the DeepL Translation Provider plugin (4.8.5) and Studio 2019. The plugin seems to have problems with mixed XML content where inline elements are declared as "not translatable". The error message we are seeing is this:

"An item with the same key has already been added."

We almost exclusively work with Docbook XML files and a customized File Type Definition that, for example, defines the Docbook element "code" as not translatable.

I tried to thin out the problem and you can use the following XML snippet with dummy text to recreate the effect:

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "">www.oasis-open.org/.../docbookx.dtd">
<chapter>
<title>Einführung</title>
<para>Auch gibt es niemanden, der den <code>Schmerz</code> an sich liebt, 
sucht oder wünscht, nur, weil er <code>Schmerz</code> ist, es sei denn, es kommt zu 
zufälligen Umständen, in denen Mühen und <code>Schmerz</code> ihm große Freude bereiten können.</para>
</chapter>

Before converting this file to sdlxliff you obviously need to adjust the filetype settings for "code" to be "not translatable".

I've already been in touch with the support teams from both SDL and DeepL. They were not able to help me but instead pointed me to this community.

SDL's support claims that the problem doesn't exist when using their own "SDL Language Cloud Machine Translation", so I reckon it must be a problem with the DeepL plugin. Can someone confirm this and/or provide a workaround?

Thank you

Patrick