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

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



Sorry for the delay in replying; I was on vacation last week.

On Mon, Aug 30, 2004 at 12:42:18AM +0200, Shot wrote:
> Branden Robinson:
> > 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.

Jeff Licquia told me this actually has something to do with a wrong or
suboptimal input manager being used by GNOME.

Jeff, can you reply to 267062-submitter@bugs.debian.org with a more
coherent explanation?

-- 
G. Branden Robinson                |     Eternal vigilance is the price of
Debian GNU/Linux                   |     liberty.
branden@debian.org                 |     -- Wendell Phillips
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature


Reply to: