Re: Garbled display of UTF-8 encoded mails

[Sven Joachim <svenjoac@gmx.de>]

On 2010-11-24 05:39 +0100, Katsumi Yamaoka wrote:

> Sven Joachim wrote:
>>> during the last weeks I encountered a problem viewing articles (mainly
>>> mails) with non-ASCII characters, e.g. a German Umlaut "Ü" is displayed
>>> as an octal digit, \334.  This happens only if the message is encoded
>>> like this:
>>>
>>> Content-Type: text/plain; charset=utf-8
>>> Content-Transfer-Encoding: 8bit
>
> It seems to be due to a bug in sender's mailer.

Not really.

> (encode-coding-string "Ü" 'utf-8) => "\303\234"
> (encode-coding-string "Ü" 'iso-8859-1) => "\334"

But in the raw article (when pressing C-u C-u g) I _do_ see \303\234, so
the charset seems to be declared correctly.  And when viewing the same
article on Gmane (which changes Content-Transfer-Encoding to
quoted-printable) everything looks fine.

>>> It does not happen with charset=iso-8859-1 or Content-Transfer-Encoding:
>>> quoted-printable (thus you cannot reproduce it with articles from
>>> Gmane).  Any idea what might have caused this?
>
>> I bisected the problem and found out that commit bda3e8962a is the
>> culprit:
>
>> commit bda3e8962af0aee90144c3ae8c5360aa4c106d94
>> Author: Katsumi Yamaoka <yamaoka@jpl.org>
>> Date:   Fri May 7 06:34:41 2010 +0000
>
> I tried old Gnus of Apr. 2010 but found no difference.

Maybe you'll see a difference in this mail.  I include characters
that cannot be encoded as iso-8859-1 and CC you.  Hopefully no-one
changes Content-Transfer-Encoding on the way.

„Schöne Grüße aus Übersee“,
Sven