Eberhard Beilharz

@mcdurdin This seems like a good idea because it allows you to pick up where you left of before you switched to another app, but I'm not entirely sure it...

Thanks for your thoughts, @mcdurdin! The context now gets always reset in `reset_context` which should take care of the points you mentioned, and also simplifies the code :smile:

This change still has a problem when the keyboard outputs a character + deadkey. In response to outputting the character we get a `ibus_keyman_engine_set_surrounding_text` call in which we call `reset_context`...

GROUP_BIONIC TEST_DEADKEY_TWOAPPS(PASSED): the result is correct, my instructions were wrong GROUP_JAMMY_X11 TEST_DEADKEY_TWOAPPS(PASSED): the result is correct, my instructions were wrong

@bharanidharanj Please make sure you use the new ibus version (check version with `dpkg -l ibus`; should be version `*sil2.1*`) and reboot after installation of ibus. Then I think the...

Works for me on Ubuntu 20.04 (Gnome with X11) with Libre Office 7.1.3.2, sil_boonkit keyboard, Doulos SIL font, Keyman 15.0.47

@mhosken Are you using X11 or Wayland? There's an open issue with Wayland support (#4273).

> X11 but Keyman 14. Do you think you did anything in 15 that would fix this? No, the changes between 14 and 15 are minimal (to non-existent) at this...

From slack: Martin Hosken: I suspect graphite in libo

gnome-terminal doesn't support surrounding text, so we have to use backspace to delete the characters. The Khmer character sequence contains a diacritic character and gnome-terminal deletes the entire cluster.