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

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



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 en-dashes, "curly" quotes, ellipsis, etc.
> I've found out that these characters should be easily obtainable with
> the compose key, and it seems they are in fact defined properly:
> 
> shot@desaxe:~$ grep pl /usr/X11R6/lib/X11/locale/compose.dir
> iso8859-2/Compose               pl_PL.ISO8859-2
> en_US.UTF-8/Compose             pl_PL.UTF-8
> iso8859-2/Compose:              pl_PL.ISO8859-2
> en_US.UTF-8/Compose:            pl_PL.UTF-8
> 
> shot@desaxe:~$ grep DASH /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose
> <Multi_key> <minus> <minus> <period> : "–" U2013 # EN DASH
> <Multi_key> <minus> <minus> <minus>  : "—" U2014 # EM DASH
> 
> Yet when I try to input <Multi_key> <minus> <minus> <period> I get
> the hyphen character right after the second <minus>; it seems that
> X is using the iso8859-2/Compose mapping instead of en_US.UTF-8/Compose:
> 
> shot@desaxe:~$ grep "<minus> <minus>" /usr/X11R6/lib/X11/locale/iso8859-2/Compose
> <Multi_key> <minus> <minus>             : "\255"        hyphen
> 
> Additionally, the <Multi_key> <a> <comma> sequence inputs aogonek, so
> I'm either using ISO-8859-2, -4 or -13 mappings (I'm betting on -2):
> 
> shot@desaxe:~$ grep -r "<a> <comma>" /usr/X11R6/lib/X11/locale/
> /usr/X11R6/lib/X11/locale/iso8859-13/Compose:<Multi_key> <a> <comma>                    : "\340"        aogonek
> /usr/X11R6/lib/X11/locale/iso8859-2/Compose:<Multi_key> <a> <comma>                     : "\261"        aogonek
> /usr/X11R6/lib/X11/locale/iso8859-4/Compose:<Multi_key> <a> <comma>                     : "\261"        aogonek
> 
> Is there a way to set X to use the en_US.UTF-8/Compose mappings?
> Shouldn't this be the default source for pl_PL.UTF-8 locale?
> 
> (I tried overwriting iso8859-2/Compose with en_US.UTF-8/Compose and it
> didn't change anything, so I guess the compose mappings must be defined
> elsewhere as well.)

Hmm, according to compose.dir, pl_PL.UTF-8 *should* be using the en_US.UTF-8
compose map.

$ grep pl_PL /usr/X11R6/lib/X11/locale/compose.dir
iso8859-2/Compose               pl_PL.ISO8859-2
en_US.UTF-8/Compose             pl_PL.UTF-8
iso8859-2/Compose:              pl_PL.ISO8859-2
en_US.UTF-8/Compose:            pl_PL.UTF-8

I'm a bit confused.  I'm using LC_CTYPE=en_US.UTF-8 myself, and getting the
en_US.UTF-8 compose map.

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.

Tagging this bug "help".

-- 
G. Branden Robinson                |     I am only good at complaining.
Debian GNU/Linux                   |     You don't want me near your code.
branden@debian.org                 |     -- Dan Jacobson
http://people.debian.org/~branden/ |

Attachment: signature.asc
Description: Digital signature


Reply to: