Paul, at 18:38 on Jun 15 1995, you wrote to Bill Grimsley...

PE> That's EXACTLY what I had decided to do, believing what I had read
PE> in NET_DEV, that the practice of using x'8d' was completely dead.

BG> Not in FMail, it ain't.

PE> Frontdoor I think it was, not Fmail.

Nope, it's 100% definitely FMail, but I think it could also be in FD too. 
Are they written by the same people, by any chance?

PE> It appears that it is dead, but not yet buried.  So now I only
PE> display x'8d' if the sender uses SOT/EOT, since that explicitly
PE> disallows x'8d' as a formatting character.  BFN.  Paul.

BG> But I use SOT/EOT, and DON'T want to see the 0x8d character.  How about a 
BG> new msged.cfg switch then, say "switch display0x8b off" ?

PE> You are confused. 

Dunno, I think I've interpreted the above correctly.  We'll see...

PE> I am now deleting x'8d' on messages that come from OTHER people and DON'T 
PE> have SOT/EOT. 

Ah, so if it appears in a Msged message with SOT/EOT enabled, that must
mean that it has been inserted intentionally, correct?

PE> No-one who uses SOT/EOT *generates* x'8d' unless it's a national character 
PE> (etc).  If you're still seeing x'8d' it's because you aren't using the 
PE> latest version 

I wasn't, as it happened.  The prior version was displaying them, both in
the message and also the quoted text, and saving it as well.  This new DOS
exe is working perfectly well here now.

PE> (I didn't crash it to David just for fun).

More fool you then.  You should have attached it to me, and I'd have sent
it to Dave for you.  Too late now though.

BTW, when are you getting your new USR 33600 DS Courier?  Soon?  I'm
beginning to get just a little pissed off with the extended delay on mine,
having ordered it some 3 or 4 months ago now.  Oh well, I suppose I
shouldn't be complaining, considering the price I'll be paying
(eventually).

Regards, Bill
@EOT:

--- Msgedsq 3.10 alpha 2