-
Notifications
You must be signed in to change notification settings - Fork 7.6k
open a normal UTF-8 file failed ! #11730
Comments
It should be a file spesific problem. |
Brackets only support utf8 encoding. We can only investigate something if we have a sample file that causes the problem. You could strip out the sensitive parts of the file and give a minimal file with the problem in brackets and attach it here for us to take a look. |
Maybe related to that one weird issue from while back where near empty json file didn't open without BOM. edit: Issue #11525 |
I found my file there is a garbled which can not be used to open brackets, maybe brackets will be better as soon as possible to support GBK |
Same issue here. With Bracket's own Getting Started index.html file. This happens with a freshly installed and unused version of Brackets. As usual with these issues, other editors open the file without a hitch and recognise it as UTF-8 showing it in their status bar. I also attempted to open the index.html file as a separate file (not as part of the default Getting Started folder which is opened at startup). But I got the same result. I already removed the Brackets and Chrome packages, then reinstalled them. With the same result. Here are some screenshots of the issue. With the issue in the English language version (root folder): With the issue in the Dutch language folder (nl folder). I also tried other language folders with the same issue as a result.: The exact same Getting Started folder (English, root folder) opens without any problems in Atom and index.html is marked as UTF-8 in the status bar : The exact same Getting Started folder (English, root folder) opens without any problems in Sublime Text and index.html is marked as UTF-8 in the status bar : EDIT: |
OK, I fixed the issue. But it happened accidentally, as a positive side effect of another issue. en_NL.UTF-8 error: en_NL.UTF-8 error fixed: Brackets fixed (after installing the locale fix): |
I think this is a bug
The text was updated successfully, but these errors were encountered: