Comment 28 for bug 204202
Revision history for this message
| Hugo Buddel (v-launchpad-hugo-doemaarwat-nl) wrote | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Doug Kelly: I tried your solution, but it does not seem to work for me on my fresh Lucid install.
Just tried something else: First layout indian, second Qwerty and then started a ping from the second layout. I could not figure out how to quit the ping (except 'killall ping'), since all my ctrl-c keystrokes printed indian characters. That cannot be useful under any circumstances it seems to me.
There are bug reports about this problem existing for other gtk apps as well, but I have not been able to reproduce the problem anywhere else besides gnome-terminal. Anyone knows another app?
E.g. similar, more general bug report:
https:/
And a later report that the fix for the above causes the symptons we see:
https:/
It is not clear to me whether this is indeed the same issue or just the same symptoms.
I cannot imagine that this is the intended behavior, for one because now it is different between gnome-terminal and xterm. But if it is, it should be more clearly documented. It is not intuitive that if you add a new layout that whether the ctrl- key mappings change depends on the order of the layouts.