Hi y'all,
retrying trinity with the new release and I'm having some problems: I'm studying Japanese, which means that I'm running ibus in order to switch keyboard layouts between English and Japanese. I've noticed that in Discord (and a the moment I can find no other examples,) it doesn't work, the keyboard layout refuses to change in Discord itself, and my shortcut keys for switching between hiragana and katakana don't work.
I've never had a problem with this in other desktop environments, I've also never had any problems with it while using a plain wm such as ice or even older ones like amiwm. Is there some sort of legacy international input going on in TDE which might interfere with how ibus works?
This is on slackware 15.0 using 14.1.5 from the Ray-V tde-slackbuilds.
Thanks, Danny
A minor correction after playing with it more: the keyboard layout is "respected", in that after switching keyboards I have a Japanese qwerty layout. Something in trinity seems to be interacting poorly with (I don't know the proper term for this) the non-committal typing? When inputting Japanese you type in qwerty and the input method "suggests" completions. a -> the hiragana for a -> various kanji that it could be, for example. That completion isn't occurring on discord, though it does seem to occur everywhere else.
On 2025-11-17 12:37:18 Daniel Wilkins via tde-users wrote:
A minor correction after playing with it more: the keyboard layout is "respected", in that after switching keyboards I have a Japanese qwerty layout. Something in trinity seems to be interacting poorly with (I don't know the proper term for this) the non-committal typing? When inputting Japanese you type in qwerty and the input method "suggests" completions. a -> the hiragana for a -> various kanji that it could be, for example. That completion isn't occurring on discord, though it does seem to occur everywhere else.
Are you using the Discord app or the web interface?
Leslie
-
Daniel Wilkins -
Leslie Turriff