Comment 3 for bug 2051371
Revision history for this message
| Egmont Koblinger (egmont-gmail) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
By the way... absolutely independently from terminals...
U+17d2 is a combining accent. When I checked (many years ago), major graphical toolkits (e.g. GTK and QT) disagreed whether the backspace keypress should delete only the combining accent, or the entire glyph (base character + combining accents) at once. GTK did one, QT did the other (I can't recall which one did which).
I don't know if the world has changed since and has settled with one of these behaviors, having found out that one of these behaviors is clearly superior to the other. I would _guess_ that not much has changed. That is, both possible behaviors are reasonable, both have their pros and cons, and probably you cannot claim that the behavior _must_ be the one you're looking for.
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.