Nicolas Obias

I'm getting the same bug too. The source of it seems to be the "Autodetect character encoding" feature in Notepad++ that seems to convert the original bytes to another format (this doesn't change the actual file), and when they're displayed in the Hex Editor, they're displayed wrong. I got the "Autodetect character encoding" idea from a github post about a similar issue here: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/3697 . It seems that particular post wasn't reported on this...

I'm getting the same bug too. The source of it seems to be the "Autodetect character encoding" feature in Notepad++ that seems to convert the original bytes to another format (this doesn't change the actual file), and when they're displayed in the Hex Editor, they're displayed wrong. I got the "Autodetect character encoding" idea from a github post about a similar issue here: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/3697. It seems that particular post wasn't reported on this...

I've tried this too, but my outputs have been varying. Here's the steps I did on these versions: Notepad++ 7.5.4 Hex-Editor 0.9.5 Open Notepad++. For repeatability, close all files. You should now have just one tab open that says "new 1" or "new 2". (As a side note, at this point, in the Encoding tab, my setting is at "Encode in UTF-8". I see a "UTF-8" label in the bottom right corner of Notepad++. After the last bug I was looking into (https://sourceforge.net/p/npp-plugins/bugs/291/), I thought...

I'm getting the same bug too. The source of it seems to be the "Autodetect character encoding" feature in Notepad++ that seems to convert the original bytes to another format (this doesn't change the actual file), and when they're displayed in the Hex Editor, they're displayed wrong. I got the "Autodetect character encoding" idea from a github post about a similar issue here: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/3697. It seems that particular post wasn't reported on this...