[mew-int 2829] Re: Encoding issues at Summary Mode

+ "Diogo F. S. Ramos" <[email protected]>:

> Harald Hanche-Olsen <[email protected]> wrote:
> >> For example, the letter "é" is sometimes shown as "=E9".
> > 
> > I guess it depends on the particular coding used for the emails.
> > Compare the Content-Transfer-Encoding header in the mails where it
> > works to those where it doesn't. Does it say 8bit for the former, and
> > quoted-printable for the latter?
> 
> Unfortunately these headers don't appear always in the e-mails. What I
> observed is that when it works, there is a Content-Transfer-Encoding
> and it is 8bit. And when it does not work, there is not a
> Content-Transfer-Encoding or when there is, as you said, it is
> quoted-printable.

Ah, but those that don't, are usually multipart messages, as indicated
by the Content-Type header. And then the Content-Transfer-Encoding is
in each part. It appears that mew doesn't give you an easy way to read
the headers for individual parts, so you'll have to check the raw
message (accessible by typing C-TAB in summary mode).

> This seems to happen especially with e-mails from gmail, which, as far
> as I can tell, do not provide a Content-Transfer-Encoding.

They sure do, if they're single part. As far as I can tell from a few
ones in my mailboxes, at least.

Anyway, it seems the trouble is that no decoding of the body is being
done for the sample to go into the message summary. I certainly hadn't
noticed, since I don't use body excerpts in my message summaries.

- Harald