Hello,

It seems like you're experiencing an issue with the DeepL plugin in Trados Studio 2022 SR2 where special characters are being converted into their HTML entities. This is likely due to the settings in Trados Studio. Here's how you can disable this behavior:

Step 1: Open Trados Studio 2022 SR2.

Step 2: Navigate to 'File' > 'Options' > 'File Types'.

Step 3: Select 'HTML 5' from the list of file types.

Step 4: Click on 'Entities'.

Step 5: Uncheck the 'Enable entity conversion' option.

If you only want to disable the entity conversion for certain characters:

Step 6: Click on 'Advanced'.

Step 7: Disable the conversion from the 'Writer settings' section.

Please note that these steps should prevent the DeepL plugin from converting special characters into HTML entities during pre-translation. If you continue to experience issues, it may be worth checking for updates to the DeepL plugin or Trados Studio 2022 SR2.

I hope this helps! If you have any other questions, feel free to ask.

Best regards,

RWS Community AI

Unfortunately, this doesn't help. Checked all of those settings, and furthermore created a simple text file with those two units shown above, and these are also being returned as the HTML codes:

For info, the original post was about an XML file type. I can't seem to get the right characters to come back from DeepL. Anyone else having this problem or can confirm that it is working for them?

Hi!

I am experiencing the same problem, any news?

Thanks

Rita

For whatever reason, this was fixed for 2022, but now I've upgraded to Trados Studio 2024 and the problem is occurring again.

Trados Studio 2024: 18.0.2.3255

DeepL plugin version: 7.0.7.0

Looking at the changelog, setting the "Tag handling" to None solves the problem (it does). However, not being able to set this XML (in our case) results in another, more seldom problem where the translation fails entirely due to a tag issue (this is documented elsewhere in the community, don't have time to search for the link, however).

It would be great if this was more robust. Thanks!

hi!

thanks for this update, i thought it was solved with latest upgrade of the DeepL plug in for 2022 (i forgot to update this issue, my apologies).

bad news for 2024..Let's see what comes from the next update of the plug in then

Rita