Hi John,
Re. the 0x08 character -- I'm going to go with "Feature". :-)
When I converted from Plain unix file to WP-2 format (inserted a default
128-byte header and converted the hard carriage returns), the resulting
.DO file loaded into the WP-2, but all the text ran together, with words
splitting across lines even in the middle of the word.
So (for my WP-2, at least) it appears to require the 0x08 characters to
act as a "soft" carriage return where a space would normally be. Those
0x08 characters split the line on the LCD, acting like end-of-line, but
not a "hard" CR. So I have some pre-processing to do, to insert those
0x08 before writing the binary .DO file.
Regards, Bert
On 11/11/22 17:45, Bert Put wrote:
I don't know if it's a bug or not. I write the raw .DO file straight to
the SD card (via the AWESOME NADSbox :-) then transfer it to my linux
box for conversion.
I convert the 0x08 to space since failing to do that would cause the
words to run together. Seems like it's being treated as a soft
line-break? I'm not converting the other special characters for
italics, bold, underline, etc. yet because I don't use them, but since
I'm stepping through the file one character at a time it should be a
trivial exercise to implement that if I ever use them. I mostly write
markdown on the WP-2 so I use the MD syntax. :-)
Anyway, I thought you'd be interested since you wrote that excellent
conversion page. It has been perfectly accurate so far.
Regards, Bert
On 11/11/22 12:30, John R. Hogerhuis wrote:
Interesting. Bug or feature?
And there are at least two wp2 firmware version. So it may differ.
ASCII 8 is backspace. I guess the thing to decide is how to use or not
use the character when converting to other formats.
If it's just an artifact of how the lines are broken over the display
(as opposed to newlines which are $0d) then it could be ignored.
-- John.
