3 ms·

Does this editor have a way to display the ASCII bytes in CP437 glyphs? I grew up reading binary files in DOS that way and I can read the glyphs much faster th

Does this editor have a way to display the ASCII bytes in CP437 glyphs? I grew up reading binary files in DOS that way and I can read the glyphs much faster than the corresponding hex values; in contrast, using dots for the non-printable characters doesn't really tell me much.

Simran-B 2y ago
You can download additional assets in the settings and then interpret data as encoded in various formats. I don't see CP437 in the list but the file format for encodings is straightforward, you can probably create a mapping easily. https://github.com/WerWolv/ImHex-Patterns/tree/master/encodings https://github.com/WerWolv/ImHex-Patterns/tree/master/encodi...
Dwedit 2y ago
The problem with CP437 is that FF, 00, and 20 are all empty space and look the same. Then there's the question about that ambiguous character that's either German Sharp S or Beta.
- ykonstant 2y ago
  I break ties by using ๐ for NULL which declutters output with lots of null bytes, and ⍽ for non-breaking space because I saw the glyph on Wikipedia.
- stavros 2y ago
  I will fight anyone who claims that a beta and an eszett look the same.
  - teddyh 2y ago
    They’re talking about CP473 character 225, (hexadecimal E1), which resembles both β and ß (depending on the exact font), and was frequently used as a stand-in for both.
    - stavros 2y ago
      Oh damn, I forgot about that code page... You're right, it's a mix between the two.