Bug#212347: en_US.UTF-8 compositions missing in /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose
hi Julien,
cool, I had already forgotten about it :)
so I'm now running Ubuntu, with X-org. But I suppose ubuntu and debian share the xlibs files, so I went ahead and tested it here:
so I just typed (using compose):
ÁÂÀÄÃáâàäã
ÉÊÈË éêèë
ÓÔÒÖÕóôòöõ
ÚÛÙÜŨúûùüũ
ÍÎÌÏĨíîìïĩ
and they all seem to be working perfect.
If the ubuntu installation can be used as a reference, pls move ahead and close the bug.
thanks :)
- jan
----- Original Message ----
From: Julien Cristau <jcristau@debian.org>
To: Jan Pfeifer <pfjan@yahoo.com.br>
Cc: 212347@bugs.debian.org
Sent: Wednesday, January 17, 2007 9:57:27 PM
Subject: Re: en_US.UTF-8 compositions missing in /usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose
Hi Jan,
about 3 years ago you reported this bug against the Debian xlibs
package:
On Tue, Sep 23, 2003 at 09:30:40 -0300, Jan Pfeifer wrote:
> many of the compositions for latin characters (accents, umlaut, etc.)
> has a "wrong" order of key strikes (Multi_Key + letter + accent, instead
> of the "natural"? Multi_Key + accent + letter). Took me a long time to
> find that out, i thought that the compositions were not working.
>
> a suggestion is to include both order of the Multi_Key compositions. The
> following simple perl script will do it (I used in my local
> instalation):
>
> perl -ne 'if ( $_ =~ m/^<Multi_key>\s+<([^>]+)>\s+<([^>]+)>\s*:(.*)$/ &&
> !("$1" eq "$2") ) { print "<Multi_key> <$2> <$1> : $3\n"; } print ;'
>
> the same suggestion would apply to Compose files for other locales.
>
As far as I can see in the current Compose file for en_US.UTF-8, most
accented latin letters can be typed with <Multi_key> <accent> <letter>.
Are there still exceptions which you'd like to have fixed?
If not I'll close this bug.
Thanks,
Julien
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
Reply to: