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

Unescaped special chars returned by DeepL

    XMLWordPrintable

Details

    • 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

    Description

      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.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. TRANSLATE-3402 Hotfix: delete deepl glossary on deleting termcollection

          • Done

          Bug - A problem which impairs or prevents the functions of the product. TRANSLATE-3400 DeepL: Create/add test for the deletion of DeepL Glossaries

          • Selected for dev

          Bug - A problem which impairs or prevents the functions of the product. TRANSLATE-3401 XML validation of XLF on export to prevent Okapi errors

          • Selected for dev

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: