Bug 97553

Summary: exmh doesn't handle UTF8 message
Product: [Retired] Red Hat Linux Reporter: Tethys <sta040>
Component: exmhAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:56:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Tethys 2003-06-17 17:18:57 UTC 
Description of problem:

When viewing Red Hat Bugzilla email, it every character is followed
by a dotted square. This is because it's treating the message as
normal ASCII/Latin1 text, rather than the UTF-8 that it is (and
that's stated in the headers).

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

How reproducible:
Every time

Steps to Reproduce:
1. Look at a RH bugzilla email in exmh
2.
3.
    
Actual results:
See attached screenshot

Expected results:


Additional info:
This is with RH9. Curiously, though, if I ssh into an RH7 box with
exmh-2.4-2, and run it X displaying to my local machine, it all looks
fine, and seems to handle the UTF8 without problems. The only relevant
environment variable are $LANG (which is en_US on RH7.2 and en_US.UTF-8
on RH9) an $LC_COLLATE (which shouldn't be relevant, but is set to C on
both machines).
Comment 1 Tethys 2003-06-17 17:20:07 UTC 
Created attachment 92451 [details]
Screenshot
Comment 2 Brent Fox 2004-04-16 21:39:11 UTC 

*** This bug has been marked as a duplicate of 89110 ***
Comment 3 Red Hat Bugzilla 2006-02-21 18:56:45 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.