[Github-comments] [geany/geany] fails to open Microsoft UTF-16LE file (MSO Word CUSTOM.DIC dictionary file) (#1238)
Colomban Wendling
notifications at xxxxx
Mon Sep 19 10:30:08 UTC 2016
Actually I tested SciTE, which is kind enough to open the file without problem, and simply showing plain bytes for the invalid ones, making line 1738 (last one) look like this:
![l1738](https://cloud.githubusercontent.com/assets/793526/18629100/cbc62c9a-7e63-11e6-867e-cc052e495886.png)
It's pretty messy but fair enough. However, we probably won't do that, because being able to have a fixed encoding in the data we load means that we have to handle encoding conversion in a single place, instead of everywhere something touches the data -- and there are a lot of code that does that, it's and editor after all.
Also, as UTF-8 can represent virtually any textual data (anything inside Unicode), it would only help with invalid input (like here) or binary data (which probably would better be handled with a hex filter). So I'm afraid it won't happen.
If someone has a nice solution though, I'd love to be proven wrong.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1238#issuecomment-247959290
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20160919/001fea35/attachment.html>
More information about the Github-comments
mailing list