[2nd attempt to post] Gentlemen, consider a message with MIME-Version: 1.0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: base64 Subject: =?utf-8?b?5YWE5byf... From: =?utf-8?b?5bGx5Z+O6aK... Note how the headers are in UTF-8, but the body in big5. But squirrelmail 1.4.19 shows them both in on one web page frame. Therefore, there needs to be some iconv'ing done to either the headers or the body. It seems our best strategy is to set Language preferences 1. Default Language : en_US 2. Default Charset : utf8 and then hope that squirrelmail will say "is this header not utf8? well let's iconv it first before sending it to the browser". Same with the body. Mutt can deal with this. Why not squirrelmail? In squirrelmail one must adjust their browser once to read the body, and then once again to make the headers sane again. It's like needing to carry around two sets of glasses. Sure, one can set the Default Language to big5, but then one cannot read the headers. And what if someone then sends you a UTF8 message. Also In http://squirrelmail.org/docs/admin/admin-7.html#ss7.4 it says "big-5, euc-kr and gb2312 characters can be displayed by Chinese and Korean translations that use those character sets." OK, I set untarred http://sourceforge.net/projects/squirrelmail/files/locales/1.4.18-20090526/all_locales-1.4.18-20090526.tar.gz into the top squirrelmail directory, and indeed the user can now have Chinese menus, etc. But it still doesn't translate the body to the same Charset as the headers. ------------------------------------------------------------------------------ ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
