-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Automatically detect encoding of the file opened #5388
Comments
Same here. Mac OSX El Captain When i open a file "Windows 1252", it changes automatically to UTF-8, then i need to reopen as "Windows 1252" and save. If i close the VSCode and open, the files will be "UTF-8" |
+1 |
How about adding setEncoding API to VSCode and creating auto detect and changing extension? |
Curren status: you always can set a workspace encoding to be used for all files of an opened folder. You can also configure this globally for any files being opened ( Things that would help a lot already is to persist the encoding for particular files when changed from the status bar. This is tracked in #10444 |
I am using Chinese Simplified Win10 now. Notepad++ are more powerful dealing with encodings, it can detect many encodings and open correctly. So I don't need to choose the encoding manually and I can search a string from files mixed with GBK-encoding and BIG5-encoding without opening them, even if the hex-codes of the string are different in GBK and BIG5. It would be good if vscode could detect encodings, at least ANSI encoding. |
Great to see plan/progress on this issue. I agree that auto detecting encoding would be a great help for large projects which may has various encoding for environments difference or historical reasons across thousands of files. Really need this feature +1. |
I expect this issue to appear in the iteration plan. |
Why is someone trying to close this issue?? |
Landed via the new |
+1 File encoding is most important issue for NON-ENGLISH PEOPLE!! |
If someone wants to verify this, the feature landed in insiders (tomorrows build): #23322 |
bpasero, the issue doesn't appear to be resolved in the new build. I replied to that thread with a demo of the persistent bug. |
@duanehutchins and I commented. in general I would suggest to report issues into new issues and not closed ones to keep the discussion separate. |
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: