Public bug reported:
Binary package hint: libgtk2.0-0
I'm guessing that GTK is the root cause of this. But basically, I can't
type certain compose sequences in Mozilla, OOo or gnome-terminal that
work in xterm or emacs. Or, the resultant sequences will be different.
For instance, in emacs or xterm if I type <Multi_key> <underscore> <A>,
I get a "ā" as defined in /usr/share/X11/locale/en_US.UTF-8/Compose.
However, if I enter it in any gtk application, I get "ª". This is
particularly irritating when entering pīnyīn, which uses characters like
"ǚ". I have yet to figure out what gtk expects me to hit to compose a
character with a caron on it, or why it doesn't just let X.org do it for
it.
I've seen this in all Ubuntu releases from Dapper to Feisty, and I
expect that this is the root cause behind Bug #98945 too.
Note I'm using xkb directly to configure my keyboard, not gnome-
keyboard-properties. Every time I start certain gnome-control-panel
applications they will override this keymap and I will have to re-run
xkbcomp to load the keymap I actually want.
** Affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
GTK's compose map is different to X's
https://bugs.launchpad.net/bugs/116183
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
