GNOME Bugzilla – Bug 62260
Bad treated accented chars (spanish Ñ, ntilde, etc.)
Last modified: 2004-12-22 21:47:04 UTC
Galeon don't shows words that contains accented chars or ntildes, like á, é, í, ó, ú, ñ, Ñ, etc. It occurs, for example, in the title bar, when the page title contains any of that characters. Example: http://www.inmoibanez.com. The page title is 'INMOBILIARIA IBAÑEZ', but Galeon shows 'INMOBILIARIA IBA', stopping when finds the 'Ñ' char. It also has problems with the Bookmarklets. Instead of to show 'Frescura de la página', it shows 'Frescura de la p', stopping in the 'á' char. There must be a problem with the iso-8859-1 support, maybe (I don't know). Thank you very much!
how is your LANG variable ?
My LANG variable is set as "es_ES.ISO-8859-1". I tried values like "es_ES", "es", "C", or simply empty (""), but in all cases the result is the same. Unsetting LANG and setting LC_ALL to any of the above values, goes to the same result. :-( If you need additional info, ask me what you want, please. Thank you!
so here is the current situation with the charset support in galeon as i see it - all the galeon data (bookmarks, history) is stored in UTF8 - we use the mozilla encoders/decoders ot convert locale<->UTF8 (hence we are subject of some of its bugs, like the CP1251 poor handling) - this conversion is dependant on the surrently active locale and not on the one of the page thas is currently being (bookmarked, saved in history) the last point is probaby the one we have to fix on the other hand, the example above does not work for me even in mozilla running under es_ES, it probably has to be tracked further i'll reopen but i am afraid we are quite near 1.0 for this to be fixed, unless of course the maintainer and the other developers dont decide otherwise
*** Bug 62765 has been marked as a duplicate of this bug. ***
*** Bug 64472 has been marked as a duplicate of this bug. ***
*** Bug 64631 has been marked as a duplicate of this bug. ***
*** Bug 63837 has been marked as a duplicate of this bug. ***
*** Bug 65272 has been marked as a duplicate of this bug. ***
let me add the comments i gave to the last duplicate its about http://www.intel.com/cn/museum/ (zh_CN) nd it use as a bookmark actually i am able to bookmark in mozilla, import the bookmark in galeon, actually see the title of the bookmark in my menu and all this as long as i am running under the LC_ALL=zn_CN locale this is a stock rh7.2 with available fonts for displaying chinese and also properly configured gtkrc files for that encoding actually galeon will not munge the bookmark title even if it cannot display it properly (because of some locale/font misconfiguration) the titles are directly imported from mozilla in UTF and are not converted in any way, you might see borkage once you attempt to edit a given bookmark title but it should work as long as your locale information is correct
*** Bug 60781 has been marked as a duplicate of this bug. ***
*** Bug 68324 has been marked as a duplicate of this bug. ***
I've added a FAQ entry at http://galeon.sourceforge.net/support/answers.php?faq=international-characters-in-titles about setting LC_CTYPE to sole this problem.
*** Bug 68598 has been marked as a duplicate of this bug. ***
*** Bug 68646 has been marked as a duplicate of this bug. ***
Isn't it a bit sad that you have to set your locale to see the correct information? What if a page that I want to view uses different characters from what I _usually_ use? Then I'd have to figure out which locale to use, and then restart Galeon?? FYI, Swedish characters et.c. in the title works just fine in both Netscape 4 and Mozilla 0.9.7.
this bug is a WONTFIX for 1.0.x and 1.2.x it will be fixed when we move to gtk+2/gnome2
*** Bug 72052 has been marked as a duplicate of this bug. ***
*** Bug 72216 has been marked as a duplicate of this bug. ***
*** Bug 83786 has been marked as a duplicate of this bug. ***
*** Bug 84243 has been marked as a duplicate of this bug. ***
*** Bug 85207 has been marked as a duplicate of this bug. ***
*** Bug 93089 has been marked as a duplicate of this bug. ***
*** Bug 93917 has been marked as a duplicate of this bug. ***
*** Bug 97294 has been marked as a duplicate of this bug. ***