Community
Participate
Working Groups
Whenever the caret is moved to Hebrew context, the IME mode is changed to Arabic. I expected it to be set to Hebrew.
Yes, I know about that. BidiUtil#setKeyboardLanguage only takes KEYBOARD_BIDI, KEYBOARD_NON_BIDI. StyledText uses this API in accordance with the level of the character in the caret position. I think this is bogus. Placing the caret on a RTL char causes the keyboard to switch to the first "KEYBOARD_BIDI" installed in your machine, moving the caret back to a LTR char will cause the keyboard to the first KEYBOARD_NON_BIDI, usually English (on English machines), but nothing guarantees it won't be German or French.
Randy, please note that fixing this bug involves implementing new APIs (to work with the keyboard layout and to detect the language/script of a char). Once this APIs are ready we would need to change StyledText. The major problem is to implement this on Linux (gtk and motif), in this platforms there is no standarts on how to change the keyboard layout/mapping. The applets to switch keyboard on Linux (gnome has one and kde has another) make this job almost impossible.
Your bug has been moved to triage, visit http://www.eclipse.org/swt/triage.php for more info.
Created attachment 156775 [details] new API for setting specific keyboard language I've implemented new API for setting specific language (and not just KEYBOARD_BIDI, KEYBOARD_NON_BIDI as it works now). This was implemented for Windows only. When it will be approved, I'll add empty APIs to other OSs.
Ira, thansk for the patch - See bug 62431
This is a one-off bulk update. (The last one in the triage migration). Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process: https://wiki.eclipse.org/SWT/Devel/Triage See Bug 518478 for details. Tag for notification/mail filters: @TriageBulkUpdate
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
