JDK-5049524 : IM switching don't work as expected under Solaris UTF-8 locale
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt:i18n
  • Affected Version: 1.4.2,5.0,6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_10
  • CPU: generic,sparc
  • Submitted: 2004-05-19
  • Updated: 2009-05-05
  • Resolved: 2009-05-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 7
1.0Resolved 7Resolved
Related Reports
Relates :  
Relates :  
Attached Java IM is expected to switch composition mode each time the CTRL+space is hit. The switching is between alphabet and Chinese modes. This works fine with ja_JP.eucJP locale. But under ja_JP.UTF-8 locale, switching will be within three modes, i.e. alphabet, Chinese, and ATOK modes. This behavior is not expected.

Platform	Solaris10
JDK		tiger beta2 b51
Locale		ja_JP.UTF-8

To reproduce,
1. Place attached Wubi.jar in jdk1.5.0/jre/lib/ext.
2. Use the attached SetSelectionKey.jar and assign any key for selecting IMs.
3. Launch Notepad demo in sdk.
4. Select host IM then enter any Japanese string.
5. Select Test IM. Try changing mode (CTRL+space) and inputting string several times then you'll see the problem.

EVALUATION Trying to find a remotely accessible Solaris 10 installation ###@###.### 2004-06-02 The problem seems to occur only when the input method is switched. Once the TestIM is selected and the app is restarted, TestIM is selected by default and the problem is not observed. It seems that on switching the input method, native input engine may not be deactivated correctly, so that it will be triggered by pressing Ctrl+Space. This problem can also be seen with JDK 1.4.2, so this is not a regression, i.e., not a Tiger showstopper item. ###@###.### 2004-06-15 This bug only happens under the system default configuration under ja_JP-UTF8 locale. After running atok12setup, you may not be able to reproduce the bug. When switching to Wubi input method, input method code first deactivates the system default input method by calling setXICFocus on the current active ic. This seems not enough under the configuration mentioned above. I inserted the call of setXICWindowFocus to set the XNFocusWindow attribute associated with the current ic to NULL and the problem is gone. However, doing that is likely causing deadlock and not recommended (I tried the same thing when fixing 6184471. Hidetoshi from Solaris xserver team suggest me not to do so. And he told me that calling XICSetFocus should be enough.). Anyway, I think this is bug inside Solaris 10 xserver. I filed bug 6214521 and after that bug is accepted, I will mark this bug as a duplicate of that one. ###@###.### 2005-1-06 02:09:23 GMT