tibbs@hpc.uh.edu <tibbs@hpc.uh.edu> wrote on Sat, 04 Sep 1999:
> It _isn't allowed do_. What you see really is the contents of the Subject:
> header and it is entirely up to the client to decode it. Even if it tried,
> how do you propose to mix up the various possible encodings into one body?
> A body part can have only one encoding, so if you get one message with its
> subject in ISO-8859-1 and another using KOI8 then what do you do? The
> solution is not to do anything and let the client do its job.
Hmmm, okay I see what you're saying. It's not possible to represent
both ISO-8859-1 and KOI8 in the same email with just a single
Content-Type header. However, I don't know of a single email client
that actually looks for and decodes a string which is represented like
=?iso-8859-1?Q?Mikko_H=E4nninen?= in the email body. In fact, if the
Content-Encoding says "8bit" or "quoted-printable", are they supposed
to do that? Or, like in the case of Majordomo digests, when there is
no header specifying content encoding?
Well, I'll ask about this on the Mutt list and see what people there
think.
It looks more like a deficiency in the email standard -- there is no
"right" way for having more than one charset text in email body, unless
you use MIME multipart messages. I actually once experimented by
setting a header of
Content-Type: multipart/mixed; boundary=--------------------------------------------------------------------
in the digest emails, and I was able to view the digests correctly with
Mutt, but I got complaints that other MUAs couldn't so removed it.
Mikko
--
// Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
If it weren't for the last minute, nothing would get done.
Follow-Ups:
References:
|
|
