Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?
> Hmm, according to compose.dir, pl_PL.UTF-8
> *should* be using the en_US.UTF-8 compose map.
Yes, it should. The catch is it doesn't. The interesting thing is,
when I overwrite /usr/X11R6/lib/X11/locale/iso8859-2/Compose with
/usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose nothing changes.
> I'm a bit confused. I'm using LC_CTYPE=en_US.UTF-8
> myself, and getting the en_US.UTF-8 compose map.
Can you compose UTF-8-only characters (as opposed
to ISO-8859-1-compatible) as well? Can you use
<Multi_key> <percent> <o> : "‰" U2030 # PER MILLE SIGN
I tried running X (GNOME) with Option "XkbLayout" "en" and locale
en_US.UTF-8, but I still can input ą (aogonek) with <Multi_key> <a>
<comma> and can't, for example, get the above-mentioned per mille sign.
> Except that it doesn't seem to work at all in bash. However, I can
> compose characters into the Mozilla location bar just fine. Weird.
Mozilla location bar is a different beast altogether - when typing
<Multi_key> <minus> <minus> nothing happens, then when I press the
third <minus> a minus appears, and in the drop-down I can see the option
to "Search for "--"", with two minuses. <Multi_key> <minus> <minus>
<period> produces a period. Also, I can't get the UTF-8-specific per
mille sign, while easily getting the <Multi_key> <a> <comma> (which is
not present in the en_US.UTF-8/Compose map). I don't think Mozilla's
location bar is a good testing-area (Galeon's location bar acts the
same as bash inside gnome-terminal, i.e. seems to use iso8859-2/Compose).
-- Shot (Piotr Szotkowski)
SCO is the thief who puts a gun to his own head
and says "give me your money or I'll shoot."
~~~ Bruce Perens, /. ~~~