Thank you, Boris. But that's weird for your case. If you have attachment, your header should have only 'Content-Type: multipart/...' instead of 'text/plain' or 'text/html'.
For my cases, they have the latter content-type and no attachment. They send me inline 8-bit muitibyte (big5) text. Mutt will depend on the charset specified in Content-Type: filed. charset-hook: This doesn't look matching my problem. If a message speicifies a strange charset, it can map it. But for my case, messages miss 'charset=big5' and mutt thinks to use some DEFAULT that I don't know where it comes from. My locale is LANG=zh_TW.big5. And my mutt has 'set charset=big5'. I don't know what is missing. best, charlie On Thu, Jan 10, 2002 at 07:41:38PM +0300, boris karlov wrote: > On Thu, 10 Jan 2002 09:48:30 +0800, Charles Jie <[EMAIL PROTECTED]> wrote: > > In our country, I used to receive messages without 'charset' specifed in > > Content-Type:, while the text body is encoded in big5. > > > > I have my mutt "set charset=big5" but the pager just display '?'s for > > such messages (other charset-tagged messages are OK). > > -- i have the same problem. check by <view-attachments> for assumed charset > - is it us-ascii? i have the last one if there's no charset part in header. > > > > > How can I do it in mutt? "set charset=big5" looks not working. > > On Fri, 28 Dec 2001 Michael Tatge <[EMAIL PROTECTED]> > in thread `charset in text/plain attachments: how to tune?' has supposed to > use <charset-hook> (e.g. charset-hook "" big5). i have `empty > (sub)expression' error in this case, but Michael does not. it's worth a try > > 10x, karlov.
msg22932/pgp00000.pgp
Description: PGP signature
