Use xattr (extended attributes) on macOS to save/load text encoding identifier with file

[gingerbeardman]

Proposal

Use xattr (extended attributes) on macOS to save/load text encoding with file.

BBEdit is the only editor I've found that already does this.

Also VSCode should honour any existing com.apple.TextEncoding and keep it when saving.

Currently the value is ignored and the encoding is guessed, often incorrectly, by looking at the contents of the file. Thankfully the xattr is kept when saving the file.

Background

• Text Encoding has to either be set manually, or guessed by scanning the file
• Both of these tasks take time

Benefits

• loading time can be reduced
• text encoding can be more persistent
• can still be changed and rewritten at any point

Details

debug command: xattr -p -l com.apple.TextEncoding "/path/to/file.txt"

output: file.txt com.apple.TextEncoding: Shift_JIS;2561

to set xattr (from terminal): xattr -w com.apple.TextEncoding "Shift_JIS;2561" "/path/to/file.txt"

References

these may help with implementation:

• node: https://github.com/LinusU/fs-xattr
• obj-c & swift: https://developer.apple.com/library/content/qa/qa1719/_index.html

• VSCode Version: 1.21.1
• OS Version: 10.13.3

[vscodebot[bot]]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[gingerbeardman]

what a waste of time @bpasero

[bpasero]

I am reopening this, it is a well written feature request with lots of description and insights. Sorry for closing it in the first place.

[gingerbeardman]

Thank you @bpasero — have a great day

[vscodenpa]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

[gingerbeardman]

Strong disagree.

4.5 years.

Multiple close and reopen.

What a farce.

[bpasero]

Please see #167999 for our plan this month to clean up and "groom" all opened issues. This issue was closed as part of that initiative.

[0xced]

Here are more references in case someone decides it would actually be a good idea to implement (it is!).

• xattr: com.apple.TextEncoding, reveals text file encoding
• Handling the text encoding attribute in text files

[gingerbeardman]

These days (6 years later) my advice is to use a different editor when working with international files.

I use CotEditor which has impeccable text encoding support due to it being a well-written native macOS app.