You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for that. I chose that encoding because 99% of the xml files had that particular encoding.
Ideally (and I tried to do this in many ways) we would extract the original encoding of the file, and use that when loading the file, then when saving the file. Unfortunately, it wasn't as straighforward as I hoped: whenever a non-ascii character showed up, the XML APIs would either throw an unexpected exception, or the characters would get unexpectedly replaced with the square character □.
For example, System/Math.xml and MathF.xml have several unicode characters that get lost after the tool runs.
The text was updated successfully, but these errors were encountered: