[Bug 117115] enter password after session lock not in basic language
https://bugzilla.novell.com/show_bug.cgi?id=117115 ------- Comment #62 from mfabian@novell.com 2007-05-10 09:34 MST ------- Dirk> I've heared that it could be possible to Dirk> distinguish between input methods and dead letter composing I think that will be very difficult. Especially the case when the dead key support is coming from an input method like scim or uim. If no input method like scim or uim is installed, the dead key support comes from X11. It is related to the Compose mechanism, the key combinations for the dead keys are also in /usr/share/X11/locale/en_US.UTF-8/Compose (search for "dead" in that file). Some years ago, all XIM servers always made using the Compose support impossible. For example, if you were using the Japanese XIM server "kinput2", you could not use Compose anymore. That is because the Compose support is an XIM and kinput2 is another one. To use Compose you set XMODIFIERS=@im=local, to use kinput2 you set XMODIFIERS=@im=kinput2. But you can choose only one XIM mechanism. scim and uim solved that problem by featuring their own, builtin Compose support. I.e. if you use XMODIFIERS=@im=SCIM (or the qt module QT_IM_MODULE=scim), your dead key and compose support comes from scim, not from X11. For the user that makes no difference, the dead keys behave the same whether they are interpreted by X11 or by scim. But for the software, this will probably be very hard to distinguish. For example, let's assume that scim is installed. Then the environment variables XMODIFIERS=@im=SCIM QT_IM_MODULE=scim will be set by default. This disables the Compose support in X11. Therefore, even if it turns out to be possible to distinguish the X11 Compose-/dead key-support of X11 in a Qt password input widget from something like scim, it won't really help that much. Because, if you disable scim you will also disable the dead key support build into scim. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com