Bug 83373 - Evolution 1.2 broke support for non code page 0 UTF-8
Evolution 1.2 broke support for non code page 0 UTF-8
Product: Red Hat Linux
Classification: Retired
Component: evolution (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
Blocks: 79579
  Show dependency treegraph
Reported: 2003-02-03 09:59 EST by Alan Cox
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-29 16:45:11 EDT
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 Alan Cox 2003-02-03 09:59:54 EST
Description of problem:

Attempting type a euro symbol, arabic, welsh, cyrillic and other characters
gives an '_' not the desired character

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


How reproducible:

Run evolution, hit new message attempt to type arabic, welsh etc. (Use character
with font set to courier to get several sets to play with)

Stuff I've checked

Locale is UTF-8 set
Message sending is UTF-8
Font selected for message display (fixed and variable) is capable of displaying
those characters

Evolution 1.0.x gets this right. Without these characters Evolution 1.2 is
basically not usable outside the USSA/Canada and parts of western europe. It
appears evolution 1.2 only displays characters in the first page of unicode
space. I've marked this high as its a revert, a bad revert at that and it makes
our primary mail app unusuable in much of the world
Comment 1 Jeremy Katz 2003-02-09 21:29:20 EST
Seems fine in evolution 1.2.2 with gtkhtml 1.1.8-1 (don't use -2, it's
definitely broken in some ways).  According to Settings->Font Preferences, my
variable width on screen font is Helvetica 12 (the adobe one) and my fixed width
is Courier 12.  Does it seem better for you with 1.2.2?
Comment 2 Jeremy Katz 2003-06-29 16:45:11 EDT
1.4 should be much happier with UTF-8

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