Thank you very much, Cristiano.
Thanks to this MAGIC setting, now the pager display right.
Frankly speaking, I've read 'charset-hook' section of the manual a
couple of times, which defines "alias". I can hardly imagine we can set
and use it this way. :-)
best regards,
charlie
On Fri, Jan 11, 2
I had the same problem an used:
charset-hook "" iso-8859-1
I think you can use:
charset-hook "" big5
This will match any message without 'charset' specified.
Hope this helps
[]'s
- Cristiano
Em Thu, 10 Jan 2002, Charles Jie escreveu:
> In our country, I used to receive messages without 'c
On Fri, 11 Jan 2002 23:05:19 +0800, Charles Jie <[EMAIL PROTECTED]> wrote:
> 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'.
-- but every attachment has its own `C
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 wi
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
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).
In Mozilla, I can have the following setting
