What you are doing with RFC 2047 encoding looks correct for the most part.
I think that your problem with Mulberry is that (the last I heard) it does
not support East Asian characters at all.
I said for the most part because you can't use RFC 2047 for the NAME=
parameter. You must use RFC
Hi Cyrus,
Current versions of Mulberry do not support 2-byte character sets, so
that is to be expected. Our next release will add full support for
2-byte charsets.
Ok. Another thing that will be nice to fix is that on Mac OS X,
Mulberry insists on setting itself as the default email client.
Hi Mark,
On Aug 19, 2004, at 19:05, Mark Crispin wrote:
I said for the most part because you can't use RFC 2047 for the
NAME= parameter. You must use RFC 2231 instead.
Ok. Thanks for the clarification.
To summarize:
(1) Envelope and bodystructure responses are always US-ASCII. Correct?
(2)
On Thu, 19 Aug 2004, petite_abeille wrote:
(1) Envelope and bodystructure responses are always US-ASCII. Correct?
IMAP responses are always ASCII, unless charset tagged in some way.
(2) Envelope's env-subject is RFC 2047 encoded if necessary. Correct?
(3) Envelope's addr-name is RFC 2047 encoded
On Aug 19, 2004, at 20:44, Mark Crispin wrote:
IMAP responses are always ASCII, unless charset tagged in some way.
Ok. Is it possible to tag a charset for envelope and bodystructure
responses?
PA.
On Thu, 19 Aug 2004, petite_abeille wrote:
IMAP responses are always ASCII, unless charset tagged in some way.
Ok. Is it possible to tag a charset for envelope and bodystructure
responses?
That's what RFC 2047, etc. do.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from