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 122377 - New 1.3.8 value of pref "intl.charset.default" screws up web pages
New 1.3.8 value of pref "intl.charset.default" screws up web pages
Status: RESOLVED FIXED
Product: galeon
Classification: Deprecated
Component: general
1.3.8
Other Linux
: Normal major
: ---
Assigned To: Tommi Komulainen
Yanko Kaneti
: 122608 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-09-15 21:20 UTC by Raul Acevedo
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Raul Acevedo 2003-09-15 21:20:20 UTC 
Galeon 1.3.8 sets the pref intl.charset.default to "Western (ISO-8859-1)",
which is different from the default value in Mozilla 1.4 and Galeon 1.3.7,
which is "ISO-8859-1".  This screws up at least the following two web sites:

1.  www.hotwire.com: fonts are too big.

2.  www.news.com: you get the text version of their site.

You can get the same problem in Galeon 1.3.7 if you set the pref to the
same Galeon 1.3.8 value.  In Galeon 1.3.8, if you set it to "ISO-8859-1"
everything works fine.

Note that on startup, Galeon 1.3.8 ignores your prefs.js setting and uses
the GConf value under /apps/galeon/Rendering/Language/default_charset and
default_charset_title.

I'm running Red Hat 9 with Ximian Desktop 2, all the latest patches.
Comment 1 Tommi Komulainen 2003-09-15 23:44:57 UTC 
In versions prior to 1.3.8 the GConf key was simply ignored, changing the value
in preferences had no effect, the Mozilla default value (ISO-8859-1) was always
used.  In 1.3.8 the GConf key is correctly used, changing the value in
preferences works correctly, we only forgot to fix the default value.  Whoops.

Fixed in 1.3.9.

The values in prefs.js are ignored for those preferences for which Galeon has a
GConf key, the value in GConf has precedence.  It is also not recommended to
edit prefs.js, user settings should be put in user.js (for both Mozilla and
Galeon.)
Comment 2 Raul Acevedo 2003-09-16 00:03:59 UTC 
Thanks for the fix!

Just out of curiousity, why does Galeon have GConf equivalents for
preferences that are available in prefs.js?  Especially when it looks
like it's some, but not all of the possible Mozilla prefs?
Comment 3 Tommi Komulainen 2003-09-18 15:19:28 UTC 
*** Bug 122608 has been marked as a duplicate of this bug. ***