Hi. On Friday 14 March 2008, Alessandro Vesely wrote: > > So in real life, utf-8 is fully usable, IMHO. > It still has to be encoded, though. Extensions such as UTF8SMTP > <http://www3.tools.ietf.org/html/draft-ietf-eai-utf8headers-09> would > allow plain utf-8 in some headers' content, but not in their names...
Ah, maybe I missed your point. Reading | The original quoting rules didn't specify unicode or utf-8 as a | possible charset, thus you should encode in an ISO-8859-X alphabet. I thought you meant that one should always MIME-encode in ISO-8859-* charset instead of encoding in UTF-8 charset. Plain, not-MIME-encoded header fields or -values are not usable, that's right, for sure. But header values being encoded with e.g. $ reformime -c utf8 -o 'รค' =?utf8?B?w6Q=?= should work well. regards, Bernd -- If a man steals your wife, there's no better revenge than to let him keep her
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
