|
Thank you. I don't care about the tool. I wanted to understand why the problem occurs.
So what seems to happen under the hood when that extension reads bytes as utf-8 (because it doesn't support other code pages):
1. Any byte 128-255 is turned into two bytes, with a leading 00, so that, for instance, "é" is turned from 233 (0xE9) to "00233" (0x00E9)
2. The reason for the question marks is that the application looks for that two-byte codepoint in the font instead of the original single-byte codepoint
|