It starts with the 0xFF 0xFE BOM, then the two-byte sequences for those 5 characters. I just ran an experiment: I created a new true UCS-2 LE w/ BOM file (with text 12345) in Notepad++, and saved it an external hex dumper xxd.exe shows: C:\Users\peter.jones\Downloads\TempData\nppCommunity>xxd ucs2le-1234.txtĠ0000000: fffe 3100 3200 3300 3400 3500. Then when you run Plugins > Hex Editor > View in Hex, the plugin takes the characters rather than the bytes. When it sees a consistent alternation of some byte followed by 0x00 byte, for the entire document, it reasonably guesses that you have a UCS-2 LE encoded file (because that’s what UCS-2 LE looks like for text), and treats each pair of bytes as a single character.
Notepad++ is a text editor, so it reasonably assumes that anything you open with Notepad++ is a text file that’s its job, after all.
0 kommentar(er)
