Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

open a normal UTF-8 file failed ! #11730

Closed
qcjackman opened this issue Sep 23, 2015 · 8 comments
Closed

open a normal UTF-8 file failed ! #11730

qcjackman opened this issue Sep 23, 2015 · 8 comments
Milestone

Comments

@qcjackman
Copy link

I think this is a bug

@abose
Copy link
Contributor

abose commented Sep 23, 2015

It should be a file spesific problem.
could you go to debug>show developer tools and copy the console logs here?
Also, Could you attach a sample file that failed to open in brackets?

@qcjackman
Copy link
Author

image
I can open it with notepad++ , and Its encoding is indeed utf8 , but when I open with brackets it warning this message

@qcjackman
Copy link
Author

image
you can see this

@abose
Copy link
Contributor

abose commented Sep 23, 2015

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.

@petetnt
Copy link
Collaborator

petetnt commented Sep 23, 2015

Maybe related to that one weird issue from while back where near empty json file didn't open without BOM.

edit: Issue #11525

@qcjackman
Copy link
Author

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

@abose abose added this to the Release 1.6 milestone Sep 24, 2015
@BobbyBabes
Copy link

BobbyBabes commented Nov 9, 2016

Same issue here. With Bracket's own Getting Started index.html file.
This happens on a fresh installation of Manjaro Minimal Net Edition (16.08) with the Linux kernel updated from 4.4 to 4.8.5. And then a medium sized installation of KDE (plasma group package; not the mammoth plasma-meta meta package).
This Google Chrome package was then installed (with pacman) from here : https://aur.archlinux.org/packages/google-chrome/
This Brackets package was then installed (with pacman) from here : https://aur.archlinux.org/packages/brackets/

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.
The Getting Started main.css file opens OK.

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):

brackets-index html-error_20161109_193330

With the issue in the Dutch language folder (nl folder). I also tried other language folders with the same issue as a result.:

brackets-index html-error2_20161109_193330

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 :

brackets-index html-error3_20161109_193330

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 :

brackets-index html-error4_20161109_193330

EDIT:
I opened Bracket's Getting Started index.html file in Chrome and hit F12 to display the console in Developer Tools. But no errors were shown. :

brackets-index html-error5_20161109_193330

@BobbyBabes
Copy link

OK, I fixed the issue. But it happened accidentally, as a positive side effect of another issue.
When I installed KDE, a non-existent locale was created : "en_NL.UTF-8".
This caused an irritating message after using the man command : "man: can't set the locale; make sure $LC_* and $LANG are correct".
I found this fix : https://github.com/PanderMusubi/locale-en-nl
After installing this fix for the locale issue, the issue with Brackets was also fixed.
I know this for a fact because I fired up Brackets prior to installing the locale fix, and was still shown the error popup. And I fired up Brackets right after I had installed the locale fix.
Then I updated Brackets from v1.7 to v1.8 and it's still OK.

en_NL.UTF-8 error:

en_nl-locale_20161115_143845

en_NL.UTF-8 error fixed:

en_nl-locale-fixed_20161115_144035

Brackets fixed (after installing the locale fix):

en_nl-locale-brackets-fixed_20161115_145223

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@abose @saurabh95 @petetnt @qcjackman @BobbyBabes and others