Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CLOSED] Dilato: Core: Brackets still not support other encodings #11342

Open
core-ai-bot opened this issue Aug 30, 2021 · 5 comments
Open

[CLOSED] Dilato: Core: Brackets still not support other encodings #11342

core-ai-bot opened this issue Aug 30, 2021 · 5 comments

Comments

@core-ai-bot
Copy link
Member

Issue by Zhanxin
Tuesday Jun 06, 2017 at 11:04 GMT
Originally opened as adobe/brackets#13422


Steps:

  1. Launch Beackets
  2. Try to open other encoding files other than UTF-8, tried with Unicode and UTF-16

Result: I always get an error that Brackets only support UTF-8 files
Expect: The files could be opened and edit
aaa.txt
error

@core-ai-bot
Copy link
Member Author

Comment by petetnt
Wednesday Jun 07, 2017 at 19:45 GMT


Encoding support is WIP in adobe/brackets#13412

@core-ai-bot
Copy link
Member Author

Comment by Zhanxin
Tuesday Jun 13, 2017 at 09:41 GMT


Tried again with build 1.10.0-17455 21, still could reproduce this issue. When open a unicode file, I would get an error message that the file is not support.
I also tried a file with encoding Chinese GB2312, the file could be opened, but the Chinese characters can't be displayed on the Brackets:
characternotdisplay

Testing file:
Unicode:
aaa.txt
GB2312:
new 1.txt

@core-ai-bot
Copy link
Member Author

Comment by Zhanxin
Monday Jun 19, 2017 at 14:06 GMT


This issue still available, if open a utf-16 LE or utf-16 BE file, the brackets would display nothing.
Attached files:
utf-be:
bcd.txt
utf-le:
abc.txt

@core-ai-bot
Copy link
Member Author

Comment by saurabh95
Wednesday Jun 21, 2017 at 09:01 GMT


We are not currently supporting files with BOM characters (UTF-16 LE and UTF-16BE)

@core-ai-bot
Copy link
Member Author

Comment by ZuoBaogang
Wednesday Jul 05, 2017 at 13:00 GMT


Retest this issue with build 1.10.0-17313, UTF-16 has been removed form the encoding list. The error message is reasonable if open an UTF-16 file.
errormessage
Close as fixed.

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

No branches or pull requests

1 participant