Comment 5 for bug 2051371

> It's never the terminal emulator (whether GNOME Terminal or any other terminal app) that decides what to print on a backspace keypress. The only thing it does is that it tells over the tty line that the backspace key has been pressed.

Makes sense. However, the user thinks of gnome-terminal because that's what he runs...

> If your input method cannot generate the symbols you need, and you need to press backspace as a workaround to get that, moreover, you need to rely on one particular behavior of backspace, then I'd argue that it's all the fault of your input method, it should be able to produce straight away whatever you wish to end up with.

Unfortunately that's not always possible. Please take a look at the wiki page under [1]. With complex writing systems there's more than one way to write a word which look 'correct' on the screen, but the order of the code points is different [2]. Not very good if you search for that word. Therefore Keyman allows to define keyboards that can auto-correct words so that you end up with the same order of the code points regardless which way you type [3]. And that requires to replace some codepoints typed previously.

> Maybe the bug you _really_ wanted to report is that gnome-terminal doesn't use the "surrounding text" feature of input methods?

That would be nice to have but until then it would be good to have backspace working properly. But as you wrote in an earlier comment that has nothing to do with gnome-terminal...

[1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion
[2] https://www.sil.org/resources/archives/91817
[3] https://help.keyman.com/keyboard/khmer_angkor/1.0.7/KAK_Documentation_EN.pdf