https://bugzilla.redhat.com/show_bug.cgi?id=2002199
--- Comment #5 from Mike FABIAN <mfabian(a)redhat.com> ---
Thank you very much for testing ibus-typing-booster with the Neo2 keyboard
layout!
The change
https://github.com/mike-fabian/ibus-typing-booster/commit/0da5d094c894355...
fixes the problem that _ didn’t trigger emoji lookup when using the Neo2
layout.
But I noticed a few other difference when using the Neo2 layout.
For example:
When typing characters like []=&$ using the Neo2 layout, they are on the 3rd
level i.e. they are typed
with “CapsLock” + something (where CapsLock is the key used for CapsLock on
most QWERTY layouts, but it is ISO_Level3_Shift on the Neo2 layout).
ISO_Level3_Shift is on AltGr (Right Alt key) on many other layouts.
In m17n-db, which ibus-typing-booster uses for transliteration,
ISO_Level3_Shift/AltGr is the “msymbol” “G-”.
So _ is typed as “G-_” with the Neo2 layout. I added “G-_” as another exception
in my patch, because it is important to be able to type _ into the preedit to
trigger the emoji lookup.
But I did **not** yet add someting like “G-&” as an exception.
That means, they when typing a & using Neo2 while a preedit is open, the
preedit is committed and the & appended.
That is probably no big problem because completing stuff ending with & probably
does not make much sense anyway.
But it is a slightly different behaviour compared to using typing booster with
a “normal” QWERTY layout.
When typing & on a normal QWERTY layout, the & is inserted into the preedit
instead of committing the preedit and appending on Neo2.
I think in these cases, this difference does not matter much.
But if you think it matters and especially if you find other, more important
problems while using typing booster with the Neo2 layout, please tell me and
I’ll think what I can do about it.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2002199