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
{{ message }}
This repository was archived by the owner on Aug 28, 2024. It is now read-only.
Rendering a text with new lines does not work consistently. Either the byte numbering is wrong or the shown hex codes. The screenshot above shows the problem with the new lines.
In case a now fully filled line has a new line, the current hex row is filled with dots "." and the text of the next line is shown in a new row in the hexdump. The byte numbering continues with a simple ROW X BYTES PER ROW numbering, which is wrong if the row above contains a new line.
In addition, the non visible chars are not shown in the hex dump. Especially the new line is different on every system (win, mac, unix). Windows uses a CR & LF, Linux a LF, and MAC a LF and classic MAC a CR. So you loose information which might be important.
The text was updated successfully, but these errors were encountered:
Rendering a text with new lines does not work consistently. Either the byte numbering is wrong or the shown hex codes. The screenshot above shows the problem with the new lines.
In case a now fully filled line has a new line, the current hex row is filled with dots "." and the text of the next line is shown in a new row in the hexdump. The byte numbering continues with a simple ROW X BYTES PER ROW numbering, which is wrong if the row above contains a new line.
In addition, the non visible chars are not shown in the hex dump. Especially the new line is different on every system (win, mac, unix). Windows uses a CR & LF, Linux a LF, and MAC a LF and classic MAC a CR. So you loose information which might be important.
The text was updated successfully, but these errors were encountered: