[Bug 1585797] Re: Distinguish between input method "XIM" and "none"
brian at ubuntu.com
Thu May 26 22:45:50 UTC 2016
I don't know if the order of inputMethods matters, but none will always
be at the end with the following change.
35 def getAvailableInputMethods(self):
36 - inputMethods = subprocess.check_output(['im-config', '-l']).decode().split()
37 - return sorted(inputMethods)
38 + inputMethods = sorted(subprocess.check_output(['im-config', '-l']).decode().split())
39 + inputMethods.append('none')
40 + return inputMethods
** Changed in: language-selector (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to language-selector in Ubuntu.
Distinguish between input method "XIM" and "none"
Status in language-selector package in Ubuntu:
Status in language-selector source package in Xenial:
language-selector-gnome includes a GUI to configure the input method
via im-config. Besides the installed IM frameworks (IBus, Fcitx, etc.)
the IM selector shows a "none" option, which actually represents the
value "xim". This was an intentional simplification, made under the
assumption that "none" and "xim" are approximately the same. However,
it has proven to be an oversimplification. For example there is a need
sometimes to control whether the X11 compose keys should be active or
This SRU adds an explicit "XIM" option, and converts the "none" option
to actually set "none".
A recent reason why an explicit "none" option is needed is Ubuntu
MATE, which does not install any IM framework by default for non-CJKV
users. Currently, when such a user opens Language Support for the
first time, the input method selector shows a blank value. With this
SRU it will correctly show "none".
An example test case would be:
* Make a fresh install of Ubuntu MATE 16.04.
* Open Language Support and find that the input method value is blank.
Low. This won't *change* the input method setting, but the currently
set value will be showed more correctly in some cases.
To manage notifications about this bug go to:
More information about the foundations-bugs