[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?


Branden Robinson:

> > 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
> Yes, this works for me on a Debian testing system (xfree86 4.3.0.dfsg.1-4).

I'm running -6 here, but it doesn't seem to matter, because...

> > 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.
> This is screwed up.  In uxterm running bash with LC_CTYPE=en_US.UTF-8,
> I *can* get per mille, but not aogonek, using the compose sequences
> you indicated.

...uxterm, you say. This gets interesting - uxterm works for
me according to the compose maps, that is it seems to be using
en_US.UTF-8/Compose; I *can* get per mille, I *can't* get aogonek.
Does this mean there's something broken in GTK/GNOME? Mozilla, Galeon,
gnome-terminal: all broken. xterm, uxterm, OpenOffice.org Writer:
all working.

-- Shot (Piotr Szotkowski)
           Human beings know a lot of things, some of which are true,
          and apply them. When we like the results, we call it wisdom.
                             ~~~ Herbert Simon ~~~


Reply to: