[Bug 919899] Re: There is no <compose> sequence for c-acute

[Carlos Andrade]

(Copy paste from https://bugzilla.gnome.org/show_bug.cgi?id=705168#c9)

I can confirm this behavior with im-ibus.

Problem appears because ibus-1.4.2/client/gtk2/ibusimcontext.c &
gtk3/ibusimcontext.c include verbatim copies of imcedilla around line
533.

I guess other input methods have been corrupted with the same "fix".
Check http://crosbug.com/11421 for details.

The main problem here is GTK using a hardcoded table to compose
characters. There is no way to have a per-locale translation for key
sequences.

A few solutions come to my mind (from dirtier to cleaner):

* Fix ibus and another input methods so they have a user-defined variable (gconf) to determine cedilla behavior.
* Fix ibus and other input methods so only languages that use "imcedilla.so" (from gtk.immodules and immodules.cache) get dead_acute + c = ç.
* Fix GTK+ to allow runtime definition of key sequences. Remove  imcedilla.so and ccedilla table from all input methods.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/919899

Title:
  There is no <compose> sequence for c-acute

Status in “console-setup” package in Ubuntu:
  Confirmed

Bug description:
  Starting with Ubuntu 11.10, the key sequence Compose+apostrophe+c
  produces the letter ç (c with cedilla) while the correct one should be
  ć (c with acute). My compose key is mapped to the right menu key.

  The problem is visible in FireFox, Thunderbird, and gedit. Strangely,
  however, Emacs does it correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/919899/+subscriptions