Hi, After reading your message, I have revised text around https://wiki.debian.org/Keyboard#Input_method_and_XIM
> -----Original Message----- > From: Vincent Lefevre <vinc...@vinc17.net> > To: Osamu Aoki <os...@debian.org> > Cc: Gunnar Hjalmarsson <gunna...@debian.org>, 988...@bugs.debian.org, brian m. > carlson <sand...@crustytoothpaste.net> > Subject: Re: Bug#988540: im-config: breaks the keyboard configuration > Date: Mon, 23 May 2022 00:54:45 +0200 > > On 2022-05-23 06:23:58 +0900, Osamu Aoki wrote: > > Anyway, XIM is dead end for some foreseeable future. My conclusion is > > "don't use > > XIM" as backend of ibus. > > https://wiki.debian.org/Keyboard#Input_method_and_XIM > > So, if I understand correctly, users may no longer be able to use xterm > when ibus is installed. Users may no longer be able to use xterm **reliably for some non-ASCII inputs** when ibus is **activated**. > After some search, I've found > > https://vas.neocities.org/custom_keyboard_layout_xkb_ibus.html > > "This guide will help you create a custom keyboard layout in xkb and > configure ibus to play along nicely." > > But this is very unclear (and perhaps wrong for other users). > That's an extreme customization. There are many ways to get to the goal. For most people, ibus supports XKB functionality defined by xkb-options with ibus's internal mechanism. As long as you use gnome-terminal etc. (not for xterm nor rxvt) to get keyboard input, ibus supports xkb-options based substitution smoothly. I hope my updates around https://wiki.debian.org/Keyboard#Multi-language_keyboard_configuration_strategy make it clear. Regards, Osamu
