ml> just so you know and can verify... here's a screen shot of your ml> message i'm replying to
Got it. From what I see it is intact. It would be nicer and more practical to have a text based hexdump instead. For example if I dump the msg_body to a file called temp.data and farm that out to xxd I get this output, suitable for insertion into a reply, which I am now doing;
Note that the actual characters in the text side of the output are periods but if you match them up with the hex you get d0 8d, d1 8d, d2 8d, and d3 83, which is perfect. Also for a quick check this should work on the console;
Or even easier and vastly less bytes in the output would be to delete all ascii and see whats left;
As you can see above all of the characters in question have survived intact and the intergity of the "CHRS: UTF-8 4" kludge has been preserved, not that it matters any as it is a totally useless entity. Obviously the work of DOS-think FTN types. :-)
The above all aside, everything looks fine. I seem to have better luck posting from the EuroPoint but once it reaches here all bets are off. I think it is someone close to here.
Het leven is goed, Maurice
... Huil niet om mij, ik heb vi. --- GNU bash, version 5.0.7(1)-release (x86_64-pc-linux-gnu) * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)
