Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-3399

Unescaped special chars returned by DeepL

XMLWordPrintable

    • Medium
    • It seems like the DeepL API has changed its default behaviour regarding the tag handling. Now we force HTML usage if not explicitly XML is given to fix some encoding problems

      In some cases DeepL returns unescaped xml special chars - please see linked TS issue for an example.

      We need to escape those in order to make Okapi export the file without errors.

      TL: Additionally here: it seems that tag_handling = xml is missing in the requests. Adding that parameter returns the correct content.

            aleksandar Aleksandar Mitrev
            marcmittag Marc Mittag [Administrator]
            Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: