https://bugs.documentfoundation.org/show_bug.cgi?id=169562
--- Comment #5 from Mike FABIAN <[email protected]> --- Created attachment 204247 --> https://bugs.documentfoundation.org/attachment.cgi?id=204247&action=edit This video shows how to reproduce the problem using ibus-m17n with the t-latn-post input method This video shows how to reproduce the problem using ibus-m17n with the t-latn-post input method: - Select “Other (t-latn-post (m17n)) - type “fox ”, this works, I get “🦊 ”. - type “dog ”, this does *not* work, I get “dog ”. The difference between the cases of typing “fox” and “dog” with the t-latn-post input method is that when typing the “x” i “fox”, that letter is “finished”, further typing could not change the “x” anymore. Therefore, the “x” is already committed when the space is typed. On the contrary, when typing “dog” the “g” is not yet committed, i.e. it is still in preedit because a following “,” could turn the “g” into a “ģ U+0123 latin small letter g with cedilla”. Thus the “g” is kept in preedit waiting for the next key typed. When the next key is a space, this “finished” the “g”, i.e. the “g” is committed and then the space is inserted after the “g”. But in that case the autocorrection to “🐕 ” does *not* trigger! Removing the space by typing BackSpace and typing the space again then triggers the autocorrection. Inserting a space after “dog” with copy&paste does not trigger the autocorrection either. -- You are receiving this mail because: You are the assignee for the bug.
