After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 110491 - Headers displayed with the wrong charset in the article pane
Headers displayed with the wrong charset in the article pane
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.14.0 betas
Other All
: Normal normal
: 0.14.0
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2003-04-10 20:26 UTC by Tõivo Leedjärv
Modified: 2006-06-18 05:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
sample message (641 bytes, text/plain)
2003-04-10 20:27 UTC, Tõivo Leedjärv
  Details
This is probably the fix, but I need to test it in a stable environment. (1.24 KB, patch)
2003-04-10 23:21 UTC, Christophe Lambin
none Details | Review

Description Tõivo Leedjärv 2003-04-10 20:26:54 UTC
Article headers should be converted from message charset to UTF-8.
Currently it is only done in the headers pane. In article pane the headers
are converted from _group's_ default charset to UTF-8. This leads to
incorrect results when the article's charset and group's default charset
don't match.

I'll attach a sample message. It is encoded in UTF-8 (except for the
subject). Take a look at "From" header.

When the group's default charset is _not_ UTF-8, "From" is displayed
correctly in the headers pane, but incorrectly in the articles pane.

When the group's default charset is UTF-8, "From" is displayed correctly in
the headers pane and also in the articles pane (as it should be).
Comment 1 Tõivo Leedjärv 2003-04-10 20:27:23 UTC
Created attachment 15622 [details]
sample message
Comment 2 Christophe Lambin 2003-04-10 23:01:34 UTC
Tõivo: any sample messages on a newsgroup I can test this with (my ISP
doesn't carry ee.spam.l_spamlist) ?

Comment 3 Christophe Lambin 2003-04-10 23:21:33 UTC
Created attachment 15628 [details] [review]
This is probably the fix, but I need to test it in a stable environment.
Comment 4 Tõivo Leedjärv 2003-04-11 06:42:41 UTC
Hmm, when I was looking for sample messages in public groups, I
noticed that all had 8-bit chars in the header encoded (for example my
name =?iso-8859-1?q?=22T=F5ivo_Leedj=E4rv=22?=). So I did not find any
"raw" UTF-8 headers.

I applied your fix and it seems to work for me (so far it hasn't
broken anything else).