Mike FABIAN

Currently, even if this feature is available, ibus-typing-booster doesn’t use it yet, it just shows in the debug log which client got focus. But I plan to use this new...

Using 1.5.26-12.1.fc36 from https://copr.fedorainfracloud.org/coprs/fujiwara/ibus/builds/ and ibus-typing-booster-2.16.7 I can see this line in `~/.local/share/ibus-typing-booster/debug.log` when the focus gets on VScode: ``` 2022-06-30 16:44:09,441 hunspell_table.py line 6137 do_focus_in_id DEBUG: object_path=/org/freedesktop/IBus/InputContext_86 client=gtk3-im:code ```...

When a new enough ibus version is used so that focus id is available and focus gets to a gtk program and the gtk input module is used, I get...

If you already have ibus-typing-booster >= 2.18.6, you can already test whether the detection of the program name of the active window works reliably. If you set the debug level...

When I tried again after moving the focus to the setup tool and back to the terminal I got: 

In case of the second screenshot I got the information `gtk3-im:gnome-terminal-server` from ibus and left it as is, in case of the first screenshot I got nothing from ibus and...

The information gotten by ibus and by my fallback may sometimes differ slightly, my fallback got `:gnome-terminal` and ibus got `gtk3-im:gnome-terminal-server` but for my idea making the matching work using...

Maybe this could be used: https://pypi.org/project/python-espeak/ It doesn’t sound great, but better than nothing and maybe good enough.

Out of interest, can you explain in a bit more detail why you want this feature? Is this to help users with impaired vision?

I thought it might be for vision impaired users. Why would it be useful as an endangered languages studies aid? The pronounciation of `espeak` sound pretty bad, very robotic, not...