Subject: Re: bug#7626: mm-charset-override-alist

From: Kenichi Handa <[email-masked]>
Date: Mon, 07 Feb 2011 14:36:16 +0900

In article <[email-masked]>, Eli Zaretskii <[email-masked]> writes:
> > >   http://lists.gnu.org/archive/html/savannah-users/2011-02/msg00003.html
> > 
> > > is shown with buffer-file-coding-system `us-ascii', whereas I would
> > > expect it to be UTF-8, because the From: header is in UTF-8.
> > 
> > > (I saved the raw message as it was found in my mailbox, in case you'd
> > > need it for analysis.)
> > 
> > Thank you.  Please send it it me.

> Attached.

Thank you.  In that mail, the first part of body explicitly
specifies this:

Content-Type: text/plain; charset=US-ASCII

So, according to this algorithm:

> > After decoding each header, if rmail-mime-coding-system is
> > nil, set it to a cons (CODING-SYSTEM . nil).
> 
> > After decoding each body, if rmail-mime-coding-system is nil
> > or a cons, set it to CODING-SYSTEM.
> 
> > After decoding a whole message, if rmail-mime-coding-system
> > is a cons (i.e. only a header part is decoded), re-decode
> > the header while binding mm-charset-override-alist to nil,
> > and set rmail-mime-coding-system to last-coding-system-used.
> 
> > Set buffer-file-coding-system to rmail-mime-coding-system.

the coding system is decided as us-ascii (the second step
above overrides a coding system from header).

---
Kenichi Handa
[email-masked]