file selection dialog box in composer is not localized Steps to reproduce the problem: On HPUX, start mozilla using ja-JP lang_pack, then start composer, type something ikn composer and then save (or save as), dismiss title prompt by type something in.

cc to tao

tao, can you offer some comment here? It seems we are using GTK's file selection widget here, and on Linux we do not have this problem. What do you think the problem might be? How does GTK widget localization works in general?

Looks like a duplicate of http://bugzilla.mozilla.org/show_bug.cgi?id=46684

Definate dupe marking as such. *** This bug has been marked as a duplicate of 46684 ***

Shanjian, I looked at the bug 46684 in 200101904 Mtrunk Win32 and Linux build. I put the Japanese characters in the filepicker.properties file of en-US.jar file, then converted to unicode. Japanese file type names are displayed correctly.

I am talking about HPUX. The problem is not found on linux and windows.

This bug is not a duplicate of 46684. In 46684, only file type is affected. But on HPUX, everything in the dialog box is affected.

shanjian, I think people are confused about your report. Could you please attach a screen shot here. DId you install the Japnese GTK locale in you HPUX ?

What do you mean GTK Japanese locale? Is it a special package?

gtk widget are localized using *.po and *.gmo files. Those file should be found under <GTK installation directory>/lib/.... However, they are missing from my installation. Need to find out when they got lost.

The binary available on HPUX is not I18n/L10n ready. I downloaded GTK source code and gettext source code, and tried to rebuild a version that can work with localization messages.

Changed QA contact to shanjian@netscape.com since IQA cannot verify this HP problem.

This problem is from GTK library. Ximian's new GTK1.2.8 will resolve the problem. I am still waiting for their final binary drop.

Ximian's latest GTK drop resolved the problem. In 601 RTM for HP, this will be resolved by using Ximian's GTK. In 6.5 and later, this problem does not exist because those widgets are implemented through Xul now.