From line in message list does not handle embedded encoding

[interp]

Names in emails with From headers that have embedded encoding like
From: <email address hidden> (Eric =?utf-8?Q?B=C3=B6se-Wolf?=)

are not displayed correctly in the message list (see attached screenshot),
but are correctly displayed in the message preview.

The message list wrongly says
Eric_B=F6se-Wolf <=?ISO-8859-1?Q?[e-mail]_>
Note how evolution seems to have changed the encoding internally from utf-8 to iso-8859-1
(bu for the mail address, not the mailer's name) and inserted
underscores (between "Eric" and "Böse Wolf" and at the end of the email message).

The message preview correctly says
Eric Böse-Wolf <email address hidden>

[interp (ubuntu-1-lysium)]

here's the screenshot mentioned in the bug report

[interp (ubuntu-1-lysium)]

here's the message source from the screenshot, stripped for privacy

[Pedro Villavicencio (pedro)]

Thanks for your report, that's known upstream comment is :
"
not Evolution's fault. it's malformed and missing the "?=" at the end of the
token.
please file a bug against the email application that was used by the sender and
point them at RFC 2047 section 8."

http://bugzilla.gnome.org/show_bug.cgi?id=498456

[Sebastien Bacher (seb128)]

The issue could be fixed in hardy

[interp (ubuntu-1-lysium)]

Pedro Villavicencio wrote (https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/183483/comments/3)
> upstream comment is :

> "not Evolution's fault. it's malformed and missing the "?=" at the end of the
> token.

Pedro, as far as I can see, this is Evolution's fault, as the bug submitter at
http://bugzilla.gnome.org/show_bug.cgi?id=498456
also replied.

> please file a bug against the email application that was used by the sender and
> point them at RFC 2047 section 8."

The attached message snippet (http://launchpadlibrarian.net/11374079/message.txt)
causing the misbehavior contains

From: <email address hidden> (Eric =?utf-8?Q?B=C3=B6se-Wolf?=)

The interesting part is "=?utf-8?Q?B=C3=B6se-Wolf?="
which matches the syntax given in RFC 2047, section 2 (and contains the pointed out "?=").
It uses a known and registered charset (utf-8) and encoding (Q = quoted printable).
"B=C3=B6se-Wolf" is the correct encoding of "Böse Wolf".

Thus, as far as I can see, the header is well-formed, so I expected
Evolution to display the name correctly.

Furthermore, as the screenshot shows, Evolution can display the name correctly,
but _only_ in the message view (bottom), not in the message list (top)
At least, Evolution should consistently show the header wrongly.

Thus, I suggest to change the status back from invalid to normal or similar.

[Peter Nagy (antronin)]

I agree and Evolution is behaving the same way for ISO-8859-2 encoding.
It displays correctly in the message preview but not in the message list.
Please correct it. See my attached screenshot of the problem.