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.

Sign up for GitHub

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

Jump to bottom

1st Hex number show wrong when it larger than 0x7f #465

Open

jingjm opened this issue Oct 17, 2023 · 1 comment

jingjm commented Oct 17, 2023

A binary file with 1st byte larger than 0x7f will show wrong. See screen copy below:
Corrent one:

Wrong one:

Owner

dail8859 commented Oct 17, 2023

Thanks for the info! It looks like Notepad Next is treating the 6-byte file as a different encoding than Notepad++.

[   150.710] D: Read 6 bytes
[   150.710] D: BOM mark not found, using uchardet
[   150.710] D: uchardet detected encoding as: 'WINDOWS-1252'
[   150.711] D: Using codec: 'windows-1252'

I'm not that familiar with different encodings but this at least points to a cause. Not sure yet how to actually fix it.

Example file:
test.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment