Package: im-config Version: 0.30-1 Severity: normal Dear Maintainer,
When choosing IBus using im-config, LibThai engine from ibus-libthai package appears to fall back from context-sensitive input validation/correction to simple key validation based on previous key press. This is an indication of surrounding text support lacking. After checking, I find im-config provides IBus support via XIM for GTK+ apps: $ echo $GTK_IM_MODULE xim $ echo $XMODIFIERS @im=ibus But this is not the case for Qt apps: $ echo $QT_IM_MODULE ibus And a workaround by switching to ibus IM module for GTK+ enables the surounding text support again: $ GTK_IM_MODULE=ibus mousepad So, the XIM backend for IBus seems to lack surrounding text support, while the GTK+ backend does not. While the ultimate solution is to add surrounding text support to IBus XIM backend, the upstream author seems to be unwilling to do so, as my filed issue [1] has been promptly closed with recommendation to avoid using XIM. [1] https://github.com/ibus/ibus/issues/1946 Therefore, I think GTK_IM_MODULE should be set to "ibus" instead of "xim" when IBus is selected, as upstream recommends. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=th_TH.utf8, LC_CTYPE=th_TH.utf8 (charmap=UTF-8), LANGUAGE=th_TH.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages im-config depends on: ii gettext-base 0.19.8.1-4 ii whiptail 0.52.20-1+b1 ii zenity 3.24.0-1 Versions of packages im-config recommends: ii whiptail 0.52.20-1+b1 ii x11-common 1:7.7+19 im-config suggests no packages. -- no debconf information
