Package: kinput2-canna Version: 3.1-4 Severity: normal
I'd like to use both the kinput2 IM and Compose/Multi_key functionality, but this apparently does not work. If I start xterm with "[EMAIL PROTECTED] xterm", then I can use the IM, but Compose+o+c does not produce the "Â"-Sign, I just get "oc" instead (which are the two characters used to compose "Â"). If I start xterm with "XMODIFIERS= xterm", then of course the IM does not work, but Compose works as expected. To reproduce, use xmodmap to map e.g. the right windows key (keycode 0x74) to Multi_key and follow the above steps. I'm not sure wether this is really a kinput2 or X11-Bug, but I think this is probably related to bug #152478, so I'm filing it here. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-ac12 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages kinput2-canna depends on: ii kinput2-common 3.1-4 Files shared among kinput2 package ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcanna1g 3.7p3-1 Canna Runtime Library ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxaw7 4.3.0.dfsg.1-10 X Athena widget set library ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii libxmu6 4.3.0.dfsg.1-10 X Window System miscellaneous util ii libxpm4 4.3.0.dfsg.1-10 X pixmap library ii libxt6 4.3.0.dfsg.1-10 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu -- no debconf information
