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 71108 - Articles encoded in iso-8859-15 are improperly displayed
Articles encoded in iso-8859-15 are improperly displayed
Status: RESOLVED DUPLICATE of bug 53465
Product: Pan
Classification: Other
Component: general
0.11.2
Other Linux
: Normal normal
: 0.12.0
Assigned To: Charles Kerr
Charles Kerr
Depends on:
Blocks:
 
 
Reported: 2002-02-10 17:31 UTC by fred
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description fred 2002-02-10 17:31:24 UTC 
When articles are displayed that have been written with the ISO-8859-15
charset (European Union, aka Latin-9), the characterset specific symbol are
displayed incorrectly; notably the euro symbol which displays as the
"generic currency" symbol which has the same encoding in ISO-8859-1. 

This is after having tried every one of my ISO-8859-15 fonts in the
"properties" panel as "article display fonts" both in the "message body"
and "message body (Monospace)" categories. Needless to say those fonts are
not at fault since they are used in a number of other apps without trouble.

It therefore seems that Pan uses the Latin-1 version of the font regardless
of the settings it is given.

Simple test, if this character : "¤" appears as the generic currency symbol
you're in Latin-1, if it's the Euro symbol you're in Latin-9.
Comment 1 Charles Kerr 2002-03-24 00:02:37 UTC 
Working in CVS HEAD now, aka Pan 0.11.90.

This version is a port to gtk2 which has built-in
support for utf8 strings & displaying them without
gtk1.2 font wierdness.

Additionally 0.11.90 handles & posts mime-specified
user-specified charsets.

If you're so inclined, I'd love to have more CVS
testers for the gtk2 port.

cheers,
Charles
Comment 2 Charles Kerr 2002-06-11 16:14:29 UTC 

*** This bug has been marked as a duplicate of 53465 ***