Hello,
On Friday, March 21, 2008 at 20:45:42 +0800, Shaochun Wang wrote:
> in gmail, it seems that the attachment filename is just weird as
> following: gb2312''%D1%A7%C9%FA%B5%F7%B2%E9%B1%ED%2Edoc
That's correct RFC 2231 encoding. So it seems that Gmail cannot
decode that, which is a bug you should report them.
>| set assumed_charset = "us-ascii:gb2312:gbk:utf-8"
You can remove the "us-ascii": It's a subset of the other charsets,
and as such is useless to check alone.
You may want to add this charset-hook (from Debian /etc/Muttrc):
| # Some GB18030 traditional Chinese mails are wrongly labelled GB2312.
| # The first charset is a superset of the second. Let's alias it, so
| # that Mutt displays such mails as if they were correctly labelled.
| charset-hook ^gb2312$ gb18030
Bye! Alain.
--
Mutt compressed folders tip for stable archive timestamp:
| open-hook \\.gz$ "gzip -cd '%f' > '%t' ; ret=$? ; touch --no-create
--reference='%f' '%t' ; exit \$ret"
| close-hook \\.gz$ "gzip -c '%t' > '%f' ; ret=$? ; touch --no-create
--reference='%t' '%f' ; exit \$ret"
| append-hook \\.gz$ "gzip -c '%t' >> '%f'"
