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

2004-09-26 Thread Branden Robinson
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

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

2004-09-26 Thread Jeff Licquia
On Mon, 2004-09-20 at 14:55, Branden Robinson wrote: On Mon, Aug 30, 2004 at 12:42:18AM +0200, Shot wrote: ...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

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

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

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

2004-08-29 Thread Shot
Hello. 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

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

2004-08-25 Thread Branden Robinson
On Mon, Aug 23, 2004 at 10:38:31AM +0200, Shot wrote: Branden Robinson: 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

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

2004-08-23 Thread Shot
Hello. Branden Robinson: 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

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

2004-08-21 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 267062 xlibs-data Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8? Bug reassigned from package `xlibs' to `xlibs-data'. retitle 267062 xlibs-data: [nls] pl_PL.UTF-8 not really using en_US.UTF-8 Compose map Bug#267062: xlibs

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

2004-08-21 Thread Branden Robinson
reassign 267062 xlibs-data retitle 267062 xlibs-data: [nls] pl_PL.UTF-8 not really using en_US.UTF-8 Compose map tag 267062 + help thanks On Fri, Aug 20, 2004 at 03:31:24PM +0200, Shot wrote: I'm using pl_PL.UTF-8 locale, and would like to be able to type certain characters, like em- and

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

2004-08-20 Thread Shot
Package: xlibs Version: 4.3.0.dfsg.1-6 Severity: normal Hello. I'm using pl_PL.UTF-8 locale, and would like to be able to type certain characters, like em- and en-dashes, curly quotes, ellipsis, etc. I've found out that these characters should be easily obtainable with the compose key, and it