0
this is a partial duplicate of the question Linux 'compose' key sequence extensions:
I am using ubuntu 13.04 with unity and I would like to have a specific composition sequence to work as defined in the X11 rules (<Multi_key> <acute> <c>
produces now "ç") and to add a new one (<Multi_key> <z> <z>
to produce "ʒ")
my ~/.XCompose contains both above rules, but the above behaviour is not here yet.
'compiled-in list', you really mean that there's a piece of software that defines a hard-coded list? do you know anything more about it? I'd like to file a bug about the (wrong) behaviour of compose acute c, but I do not know who to alert about it. – mariotomo – 2013-07-30T12:26:59.787
@mariotomo: Yes. When GTK is being compiled, the default X11
– user1686 – 2013-07-30T12:35:57.473Compose
file is transformed by a script into a C headergtkimcontextsimpleseqs.h
, which becomes part of the compiled input method. See also the comments at the top of that file. Bug reports go to GNOME Bugzilla forgtk+
.@mariotomo: However, it seems that the header is only regenerated manually every now and then, so it might have gotten out-of-date. – user1686 – 2013-07-30T12:37:42.183
but this way I cannot use shift-ctrl-u to type in an arbitrary unicode character, can I? – mariotomo – 2013-07-30T13:21:29.463
and there is no way to alter it once it has been compiled? no extra configuration files? – mariotomo – 2013-07-30T13:22:50.563
No. If you want to configure it, use
xim
(X11's default input module). – user1686 – 2013-07-30T13:53:34.990regarding the custom composition rules, I find your answer perfect, but for the ć, I have opened this bug report. https://bugzilla.gnome.org/show_bug.cgi?id=705168. maybe you have some ideas/corrections about it?
– mariotomo – 2013-07-30T19:45:52.157