Comment 43 for bug 369150

To implement what follows "here's what should done by MUAs" in comment #5 (which I'm aware is what Pine does), we may have to do a rather major change. It also leads to a trouble when you send to a "not-so-smart" MUA (e.g. most of web mail services) which cannot deal with RFC2047-encoded words in charset other than that of the message body. [1] So, we might have to find other "ad-hoc" ways.

[1] Consider the following scenario
1. You receive a French email in UTF-8 with its sender's name and subject in RFC2047 with 'UTF-8' as charset
2. You reply to it while copying it to another person at hotmail.com (whose default setting is Windows-1252.) Because you know that hotmail cannot deal with UTF-8, you set 'Character Encoding' to Windows-1252
3. If we just copy RFC2047-encoded person's name and subject (with 'Re:' prepended) with charset=UTF-8 instead of decoding and reencoding it in Windows-1252, your recipient at hotmail wouldn't be able to read them.
4. Needless to say, this is hotmail's fault, but it's what we have to think about.