GNOME Bugzilla – Bug 559909
Cannot compose a with cedilla [regression]
Last modified: 2008-11-26 10:31:27 UTC
Please describe the problem: Since I upgraded to GTK+ 2.14.4 on Debian/experimental I lost the ability to enter latin a with cedilla by composing it with the comma or cedilla keys. I can compose e with cedilla, g with cedilla and many others, but not the a, which is needed to write properly in Polish. For what it's worth, I have looked at the Compose.pre file from X.org, and it's not there, but it used to work with previous version of GTK+ (up to 2.12). I also loved in the previous version that composing worked too by entering the letter first and then the diacritic mark. It made typing easier. Steps to reproduce: Enter <Compose> <comma> <a> and see nothing happens... Actual results: The bell beeps. Expected results: The latin a with cedilla should appear. Does this happen every time? Yes. Apparently "by design." Other information: I'm glad to hear GTK+ now has 10 times as many symbols compositions as before, but it'd be great if the old ones worked, too.
If you know of any other combinations that were lost, please list them here. It would also be great if you could file a bug against X in bugs.freedesktop.org to get the missing combinations into the X compose file, eventually.
Simos, does your compose file parsing machinery support a lookaside to add some extra sequences ?
Here is a bunch of bugs where we added extra sequences in the past, might be worth checking if we lost any of those: bug 107507 bug 93421 bug 349638 bug 172653
Making sure that we cover all sequences shown in http://en.wikipedia.org/wiki/Compose_key would also be nice.
Matthias, it does not support to use two Compose files yet. What I have in mind is to add a 'Compose.gtk' file with those compose sequences, and have that file in gtk+/gtk/. Primarily, such a file would be useful because in platforms such as Windows, I think it would require some additional intermediate sequences on top of what X.Org offers. This relates to compose sequences with two or more dead keys. If someone with Windows is able to verify, it would be great. Regarding the cedilla Multi_key compose sequences, it is simply a bug in the X.Org compose sequences. The sequences <Multi_key> <comma> <a> : "ą" <Multi_key> <comma> <A> : "Ą" <Multi_key> <cedilla> <a> : "ą" <Multi_key> <cedilla> <A> : "Ą" are missing. Reporter, could you please have a look at https://bugs.freedesktop.org/show_bug.cgi?id=18501 and provide some input? Reporter, you can also type ąĄ and many other characters (áéâêäëãẽàèǎěăĕąę) if you use an appropriate layout (such as the default for GB Englsh, or US International).
I can't seem to get the feminine ordinal (Unicode 00AA) or masculine ordinal (00BA) signs by typing "_a" or "_o" in any combination. Instead, I get an "a" or "o" with an overline. This may be good for some languages, though, in which case a different combination should be used for ordinals. I'm using a "Generic 105-key (Intl) PC" keyboard with the "USA" layout, on Gnome 2.24.1 (Ubuntu 8.10) (In reply to comment #4) > Making sure that we cover all sequences shown in > http://en.wikipedia.org/wiki/Compose_key would also be nice. > If we're also using this bug report to add wishlist items for the compose keys, here are a few math symbols I can think of: sign ...................... key combo --------------------------------------- not equal ................. =/ or /= greater-than-or-equal ..... >= or => less-than-or-equal ........ <= or =< approximately equal ....... ~= or ~~ right arrow ............... --> left arrow ................ <-- right fat arrow ........... ==> left fat arrow ............ <== therefore (u2234) ......... .: because (u2235) ........... :.
Isn't this a duplicate of bug 557420?
Both reports describe effects of the same bug. I am marking this as DUP of bug 557420. *** This bug has been marked as a duplicate of 557420 ***