Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: emacs-w3m@namazu.org
Subject: Re: why Chinese just shown in byte codes?
Date: Mon, 20 Jun 2011 09:54:39 +0900	[thread overview]
Message-ID: <b4mvcw1fhkg.fsf@jpl.org> (raw)
In-Reply-To: <87wrgi3889.fsf@jidanni.org>

jidanni@jidanni.org wrote:
> Why is the following message's Chinese just displayed in octal codes,
> and not real Chinese, like mutt(1) can see?
[...]
> Maybe the problem is in
> "
> Content-Type: text/plain; charset="UTF-8"
>  Digest for Group:
>    Chinese Speakers
>    http://www.couchsurfing.org/group.html?gid=42773
>    Last Group Digest Sent:  Jun 19 12:55 am
> "

That's indeed just the cause (w3m is not, as Steinar Bang said).

> Well mutt(1) can deal with it. Maybe gnus/w3m could be less strict about
> formatting?

I don't know mutt, but I don't think every MUA worth dealing with
such a broken thing.  If you often get such mails, this will help
(waste time a bit even with normal mails, though).

(defadvice rfc2231-parse-string (before separate-charset-token activate)
  "Separate charset token being not terminated."
  (if (string-match "\\(charset=[^\t\n ]+\\)[\t\n ]*[^\t\n ;]" (ad-get-arg 0))
      (ad-set-arg 0 (concat (substring (ad-get-arg 0) 0 (match-end 1))
                            ";"
                            (substring (ad-get-arg 0) (match-end 1))))))



  parent reply	other threads:[~2011-06-20  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19  1:44 jidanni
2011-06-19  9:13 ` Steinar Bang
2011-06-20  0:54 ` Katsumi Yamaoka [this message]
2011-06-20  1:18   ` Katsumi Yamaoka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4mvcw1fhkg.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-w3m@namazu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).