blilly(_at_)erols(_dot_)com (Bruce Lilly) wrote on 24.12.02 in
<3E088D4B(_dot_)5050508(_at_)alex(_dot_)blilly(_dot_)com>:
The best solution would be to continue the RFC 1036 practice of using the
Internet text message format, i.e. there would be no untagged, unencoded
illegal octets or superfuous "parameters", and gateway header
That, however, is not the existing real world practice. Real world
practice among those actually using non-ASCII characters is, not for
everyone but for huge numbers of messages, to have untagged non-ASCII
stuff in headers in whatever the local charset happens to be.
(And, of course, 1036 did _not_ use the Internet text message format, it
defined its own that looked similar but had lots of important
differences.)
MfG Kai