Unescaped special chars returned by DeepL

XMLWordPrintable

    • Medium
    • None
    • 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
    • None

      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.

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

              Created:
              Updated:
              Resolved:
              None
              None