As Ned is so fond of saying, "That dog don't hunt."
I thought that was Jeff Case's saying...
It is, although I've been known to borrow it...
Text/enriched is
probably more widely deployed in mail programs than text/html, it has a
much simpler syntax (only "<<" for quoting the "<" symbol and "<nofill>"
for doing forced-wrap text), and still people wouldn't accept it, let alone
generate it reasonably. I think using any kind of internal markup that is
not fully text/plain compatible is a losing battle.
Okay, so this really is the quoted-printable problem all over again.
People won't generate that reasonably either...though I've always
wondered if this is because it seems too difficult, or they haven't
tried, or they didn't think of it, or they just don't care.
Yes, it pretty much is. But a key difference is that Randy has come up with
something that is _completely_ compatible with the existing format.
Quoted-printable, text/enriched, and certainly text/html don't even come close
by comparison. Randy's format has no markup, no funny characters, nothing. Just
some spaces at the ends of lines.
This is as friendly as it gets to existing agents, yet lets more advanced
agents reformat the parts where it is OK to reformat.
Ned