ac>> ASCII: 141 : Hex: 0x8D : ""

> That got stripped.  I wonder who did it, as my software won't.
> Or wouldn't if you had used SOT/EOT anyway.  Yeah, that's how
> it works.  BFN.  Paul.

ac> There's no guarantee that a message that uses SOT/EOT won't have 0x8D 
ac> stripped though, unless we all use SOT/EOT-compliant mail processors (which 

There are very few mailprocessors that will strip the x'8d', so 
that isn't an issue.  What is an issue is what your mail-reader
will do.  For a very brief time I stopped MSGED/SQ from stripping
x'8d' on messages.  Until I suddenly found out (from Bill and David)
that there are a lot of messages with soft-CRs in them after all
(NET_DEV had told me no-one used them anymore).  I then changed the
logic to only preserve x'8d' if SOT/EOT were present.  Because the
SOT/EOT spec mandates that x'8d' is a real character, not a soft-CR.
It's a good solution.  If you're interested in getting your text
through, protect it with SOT/EOT.  If you aren't interested, you are
at the mercy of the traditional algorithms.  BFN.  Paul.
@EOT:

---