Issue #1367: Special XML characters (<"&) are not encoded properly... (okapiframework/okapi)
jhargrave-straker
https://bitbucket.org/okapiframework/okapi/issues/1367/special-xml-characters-are-not-encoded
jhargrave-straker:
In XLSX files that contain a "table1.xml" within the internal zip structure, if the `<tableColumn>`'s `name` attribute contains an apostrophe in the translation, it's escaped an extra level \(`&apos;` instead of simply `'`\). This causes the translated file to not open correctly in Excel post-translation \(though I'm not sure why the extra escape causes an error rather than simply incorrect display\).I'm going to try to scrub client-specific text from one of the files that has the issue, run it through "translation", and get those files to you. I'm also going to see if this happens with other special XML characters - `<"&` - as well as the apostrophe.
Probably an issue with the XLIFF extraction as these get double escaped. Shouldn’t be an issue with the new JSONL extraction format.