Take a look at what Dan says. It is the USER AGENT that should present
the headers in a "readable" way to the user. The conclusion of this is
that WE DONT NEED local characters in the headers. We can USE the
"content-type: message/iso-8859-2" form (see chapter 5.4 in the draft).
No, we can't. Mark Crispin has decided, in his infinite wisdom, that
a content-type "message" can't have a transport encoding, and therefore
it can only contain characters that can be represented in seven bits.
iso-8859-2 happens to contain characters which cannot be represented
in seven bits.
You lose.
Sven-Ove Westberg, CAD, University of Lulea, S-951 87 Lulea, Sweden.
Internet: sow(_at_)cad(_dot_)luth(_dot_)se
--Johnny