Bug 80036 - iso8859-1 extended chars displayed incorrectly
iso8859-1 extended chars displayed incorrectly
Product: Red Hat Linux
Classification: Retired
Component: evolution (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2002-12-18 18:50 EST by Michael Wardle
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-09 22:08:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Wardle 2002-12-18 18:50:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202

Description of problem:
When viewing a ISO8859-1 (Latin-1) encoded plain text message in
Evolution, extended characters appear incorrectly (for instance, an
o-umlaut appears as an odd symbol that looks something like an X or
an asterisk).

I will fetch the latest Raw Hide package and test that just in case
this issue has been fixed recently.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:


Additional info:

This is using evolution-1.2.0-2 downloaded a couple weeks ago from
Raw Hide.  I have a feeling this issue also existed in evolution 1.0.x.

I have tried various different fonts, but the characters are still
rendered incorrectly.

I am using a mostly standard Red Hat Linux 8.0 with en_AU.UTF8 locale.

The mail message I saw this with most recently had specifically
stated it was encoded using ISO8859-1, as the headers contained:
Content-Type: text/plain; charset=iso-8859-1
Comment 1 Jeremy Katz 2002-12-29 03:51:28 EST
Is this any better with 1.2.1 currently in rawhide (and more importantly, the
newer gtkhtml)?  If not, what are your font settings set to?
Comment 2 Jeremy Katz 2003-02-09 22:08:52 EST
Closing due to inactivity

Note You need to log in before you can comment on or make changes to this bug.