Re: [Evolution] UTF-8: Non-ASCII in subject: –
- From: Milan Crha <mcrha redhat com>
- To: evolution-list gnome org
- Subject: Re: [Evolution] UTF-8: Non-ASCII in subject: –
- Date: Tue, 06 Jan 2015 17:13:50 +0100
On Sun, 2014-12-21 at 19:53 +0100, Paul Menzel wrote:
Hmm, I do not have any problems with this message either.
Hi,
Paul sent me the email and I see the difference there. While this
message has the dash in subject encoded as:
=?utf-8?q?=E2=80=93?=
the original message, which is printed incorrectly in the message
list, has it encoded as:
=?ISO-8859-1?Q?=96?=
The later is transformed into UTF-8 and then into HTML as:
–
while the former is transformed into HTML as:
–
Both are properly shown by the WebKit, but not by cairo/pango (I
printed the subject text into the terminal and it also shows the dash
as an unprintable character there, the same way evolution's message
list does).
When I convert this 0x96 character from iso-8859-1 to utf-8 using
iconv [1], which the Camel (in evolution-data-server) does too, I get a
two-byte sequence 0xC2 0x96, just like in Camel.
Do not ask me why the Webkit can handle the letter properly, I do not
know it. Maybe they use a different converter, which knows that dash.
Bye,
Milan
[1] The command I used was:
$ iconv -f=iso-8859-1 -t=utf-8 <a.txt >b.txt
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]