Evolution could deal better with characters in windows-1252 but not iso-8859-1
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gtkhtml3.14 |
Confirmed
|
Wishlist
|
|||
| gtkhtml3.14 (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Binary package hint: evolution
Ubuntu 9.04. evolution 2.26.1-0ubuntu1
I'm using the Exchange connector but I doubt that this affects Evolution's behaviour.
I received a multi-part HTML email from another user of the same Exchange server. Despite the HTML part starting with
Content-Type: text/html; charset=
Content-
it contained the quoted character "=92" which is the windows-1252 code for a curly quote.
This appeared in Exchange as a "character not available in font" box containing "0092".
Of course this is clearly Exchange or Outlook's fault for claiming iso-8859-1 but then using windows-1252 characters. But having said that, it would seem to be quite easy for Evolution to work around this and show the expected glyph. The characters in that range are considered to be control characters in iso-8859-1 and could therefore be automatically mapped to their corresponding Unicode code points based on the windows-1252 encoding. See http://
| affects: | evolution (Ubuntu) → gtkhtml3.14 (Ubuntu) |
| Mike Crowe (mac) wrote | #1 |
| Sebastien Bacher (seb128) wrote | #2 |
| Changed in gtkhtml3.14 (Ubuntu): | |
| assignee: | nobody → Ubuntu Desktop Bugs (desktop-bugs) |
| importance: | Undecided → Low |
| Mike Crowe (mac) wrote | #3 |
| Pedro Villavicencio (pedro) wrote | #4 |
| Changed in gtkhtml3.14 (Ubuntu): | |
| status: | New → Triaged |
| Changed in gtkhtml3.14: | |
| status: | Unknown → New |
| Changed in gtkhtml3.14: | |
| importance: | Unknown → Wishlist |
| status: | New → Confirmed |
I've reproduced this using a specially crafted plain text email too:
Content-Type: text/plain; charset=
Content-
To: Recipient <someone@somewhere>
From: Sender <someone@somewhere>
Subject: A test
There=92s
.