Checkpoint data is now shown in a uniform way, whether it is binary or text data. Furthermore, the editor does not show the difference between line ending LF and line ending CRLF.
These issues can be addressed as follows. First we add a drop-down menu with the following options:
- Text.
- Control characters.
- Binary.
"Binary" shows the byte codes as hex, something like 01 AB 23 3B. "Control characters" shows text in such a way that control characters are clearly visible. Someting like:
The cow-->LF>
Jumps
Over the-->.fence
The dot stands for a space here and is a regular dot.
If there is some standard to display text this way that we should follow that instead of using my invention.
--
When the user switches between Text, Control characters and Binary, edits are lost. When Text is selected, we should show a label with the line ending: NONE, LF or CRLF.
Checkpoint data is now shown in a uniform way, whether it is binary or text data. Furthermore, the editor does not show the difference between line ending LF and line ending CRLF.
These issues can be addressed as follows. First we add a drop-down menu with the following options:
"Binary" shows the byte codes as hex, something like
01 AB 23 3B. "Control characters" shows text in such a way that control characters are clearly visible. Someting like:The cow-->LF>
Jumps
Over the-->.fence
The dot stands for a space here and is a regular dot.
If there is some standard to display text this way that we should follow that instead of using my invention.
--
When the user switches between Text, Control characters and Binary, edits are lost. When Text is selected, we should show a label with the line ending: NONE, LF or CRLF.