237211 - gtk2 build: Russian window is escaped : \x{04xx}....

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Jungshik Shin]

The following was sent to the gtk-i18n list.

----------
Hello!
It's a small glich, but i alwasy get it if using gtk2.
Well, i compiled firefox with a gtk2 toolkit, and you can see a
screenshot http://fenixhost.com/firefox.png, as you can see there all is
ok with russian in the document, but not in the window title (codes
\x{0424} ...)

I recompiled firefox using gtk toolkit (gtk1), here is a screen shot
http://fenixhost.com/firefox-gtk1.png, as you can seee there all is ok
either in documtn body, or window title...

I'll keep searching for solution, but may be someone already solved such
trouble.

It's just a window title bug, everything else works good with russian
(bookmarks names, text etc...)

Comment 1

[Jungshik Shin]

I have yet to check this out. I don't think I've seen this, but I may have just
missed it. 

Comment 2

[Christopher Blizzard (:blizzard)]

We just use gtk2's internal methods for setting the window title.  Also, what's
the window manager?

Comment 3

[Jungshik Shin]

Both gnome2-metacity and kde don't have this problem.

He uses fvwm2. Nonetheless, it's strange that gtk1 works fine while gtk2-build
doesn't. His locale is ru_RU (not ru_RU.UTF-8). gtk2's internal method may have
a problem (such as supporting only UTF8_STRING ?)

Comment 4

[Jungshik Shin]

Compare 

http://lxr.mozilla.org/seamonkey/source/widget/src/gtk2/nsWindow.cpp#921

and 

http://lxr.mozilla.org/seamonkey/source/widget/src/gtk/nsWindow.cpp#2275

Is gtk_set_title in gtk2 different from gtk_set_title in gtk1? 

Comment 5

[Christopher Blizzard (:blizzard)]

The code included in gtk2 is supposed to do all that under the covers.  It might
be that fvwm2 uses only the local encoding and gtk2 doesn't set that?

Comment 6

[Jungshik Shin]

> fvwm2 uses only the local encoding and gtk2 doesn't set that

That's what seems to be happening as I wrote in comment #3.  gtk2 doesn't seem
to set COMPOUND_STRING (locale encoding is not used in inter-client
communication). That is, it seems to set only UTF8_STRING (and perhaps STRING.)

I was a bit confused by the fact that kwin (KDE3) doesn't have any problem even
under ru_RU, ko_KR and ja_JP locale. However, that's probably because kwin
supports UTF8_STRING while fvwm2 does not.

After a little more investigation, this bug  has to be closed as invalid.