Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 154359

Summary: [gimlet] lang label out of sync with client
Product: [Fedora] Fedora Reporter: Lawrence Lim <llim>
Component: iiimfAssignee: Jens Petersen <petersen>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: eng-i18n-bugs, tools-bugs
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 12.2-4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-12 08:49:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 125997    

Description Lawrence Lim 2005-04-11 03:47:01 UTC
Description of problem:
GIMLET in the latest iiimf does not reflect the locale of the LE in used
properly. It is always displaying the locale of the LE used prior to the new LE
selection.

Version-Release number of selected component (if applicable):
iiimf-12.1.1-11.svn2435

How reproducible:
Always

Steps to Reproduce:
1.log in at gdm with ja locale
2.starting with GIMLET with only japanese LE
3.add xcin and hangul LE to GIMLET
4.start gedit and select xcin for traditional chinese input
5.observe the GIMLET, it is still reflecting ja instead of TC, input is OK
6.select hangul LE for input in the gedit application
7.observe the GIMLET now reflects TC instead of KO
  
Actual results:
GIMLET not reflecting the proper locale of the LE being in use

Expected results:
GIMLET shuold reflect the locale of the LE selected

Additional info:
Similar behaviour observed with gnome-terminal and gedit

Comment 1 Jens Petersen 2005-09-12 08:49:32 UTC
I believe this was resolved before FC4.  Closing for now.