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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悶 Cannot show the contents of text files that are not UTF-8 encoded #1726

Closed
plbstl opened this issue May 20, 2024 · 0 comments 路 Fixed by #1727
Closed

馃悶 Cannot show the contents of text files that are not UTF-8 encoded #1726

plbstl opened this issue May 20, 2024 · 0 comments 路 Fixed by #1727
Labels
bug Something isn't working duplicate This issue or pull request already exists triage needed

Comments

@plbstl
Copy link
Contributor

plbstl commented May 20, 2024

Description

CodeEdit cannot show the contents of text files that are not UTF8 (and ASCII) encoded. They show up as empty.

This might be a duplicate of #1263 and it is not related to #1202 as that has to do with writing to a file.
Xcode shows file contents regardless of the Default Text Encoding Setting.

To Reproduce

  1. Open CodeEdit
  2. Select a text file that is not encoded in UTF-8

Example files can be gotten from: https://github.com/stain/encoding-test-files

Expected Behavior

CodeEdit should at least show contents of the opened file, even if characters are replaced with question marks.

Version Information

CodeEdit: 0.1.0-alpha (38)
macOS: 14.4.1
Xcode: 15.3

Additional Context

No response

Screenshots

cannot.view.text.files.that.are.not.UTF8.encoded.mov
@plbstl plbstl added the bug Something isn't working label May 20, 2024
@github-actions github-actions bot added duplicate This issue or pull request already exists triage needed labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists triage needed
Projects
Status: 馃弫 Complete
Development

Successfully merging a pull request may close this issue.

1 participant