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

[Frederik Elwert]

I just discovered a work-around that is easier than setting an
environment variable (GTK_IM_MODULE), but effectively does the same: In
the text field where you want to type, e.g. gedit, right-click and
select “Input Methods → X Input Method” from the context menu.

So this behavior seems to stem from the default input method, IBus. This
might explain why editing the files under /usr/share/X11 had no effect.
So maybe this bug is not affecting console-setup, but IBus instead? Or
does anyone know where the pre-configured IBus input method gets its
mappings from?

-- 
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