You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the GBK format, the character in the last position should not be displayed. It seems that this might be difficult to implement, which may be why each character is displayed, leading to what appears to be garbled text occupying the position.
Hi,
I believe this is just misunderstanding of how hex editors work. Hex editor is not text editor as it works with raw binary data and it has just a text preview where for each byte position a single character is decoded.
This means that as it works by design for multi-byte character sets/encodings (applies to both UTF-8 and GBK) you should not expect a coherent text / character sequence in preview.
BinEd provides editable string sequence decoder in parsing panel which decodes short text from current cursor position.
In contrast example of decoding from second byte which would be invalid in text editor / in the middle of first character:
I'm not aware if there are some hex editors which would provide better approach to this / there could be maybe added some dynamic mode with preview generated from current cursor position, but I have no plans for that...
After translating a piece of text from UTF-8 to GBK encoding, the original characters still remain.
The text was updated successfully, but these errors were encountered: