Closed Bug 7822 Opened 26 years ago Closed 26 years ago

[PP]support the locale in menus on Linux

Categories

(Core :: Layout: Form Controls, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: erik, Assigned: erik)

References

Details

(Whiteboard: Checked in a fix)

As a first step towards fully multilingual menus on Linux, we need to support the current locale by converting Unicode to the locale encoding before passing the strings to the menu items.
Status: NEW → ASSIGNED
Target Milestone: M7
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I checked in a fix. To test this, you will need to set the locale on your Unix box before invoking apprunner. For example: setenv LANG ja_JP.ujis On RedHat 5.2, you also need the following RPMs installed: skewer:/builds/erik/libwcsmbs-0.0.4-SNAP.i386.rpm skewer:/builds/erik/wcsmbs-locale-ja-0.4.6-SNAP.i386.rpm To use these, you also need to set the following: setenv LD_PRELOAD /lib/libwcsmbs.so Sorry, but that's the current state of affairs on RedHat 5.2, our reference platform.
QA Contact: phillip → amasri
Changed QA contact to amasri@netscape.com.
Summary: support the locale in menus on Linux → [PP]support the locale in menus on Linux
Status: RESOLVED → REOPENED
QA Contact: amasri → chjung
Change QA contact to myself. This bug fix works fine for normal menu labels. But the other menu labels which have sub-menus, still display dot characters "." instead of Japanese characters. I verified it on M7-06-15-08. Therefore, I'll reopen this bug for remain issue.
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: --- → FIXED
Whiteboard: Checked in a fix
*** Bug 6542 has been marked as a duplicate of this bug. ***
Status: RESOLVED → VERIFIED
I verified the bug fix with M7-06-16-99-08 It worked fine. Great job, Erik.
Moving all Widget Set bugs, past and present, to new HTML Form Controls component per request from karnaze. Widget Set component will be retired shortly.
You need to log in before you can comment on or make changes to this bug.