touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #02213
[Bug 1235105] Re: Wrong dead key on us-intl keyboard layout
My understanding was that the changes to the International keyboard
was that it should be truly international, and support *all* of unicode.
Most of us writing in English would just as soon only have a little bit of
International.
There is a way to set up your input any way you want, and I've taken
advantage to create my own ~/.XCompose file, which, if installed at
/usr/share/X11/locales/C/Compose, and ENV set LC_CTYPE=C, will
work, by restoring the ISO-8859-1 input you crave, and it has a work-
around for that nasty bug where non-dead uses of the deadkey are
ignored, rather than treated literally. I'm happy to share that code,
if people want it. I think the current Compose file for ISO is just
wrong, and consider my re-write to be a bug fix. So, set your locale
to C, thats a start, and then use .XCompose to change the things you
can't stand.
Basically, I added lines like:
<dead_acute> <t> : "'t" # apostrophe,
t
only I did it for the whole alphabet.
--nerodog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1235105
Title:
Wrong dead key on us-intl keyboard layout
Status in “xkeyboard-config” package in Ubuntu:
Confirmed
Bug description:
Since first version of Ubuntu I used (6.06), when I press "Apostrophe"
key and then "c" the result was "ç".
However, now when I use the same sequence in Saucy Salamander (up-to-
date) I get "ć".
Keyboard Layout: USA (international with dead keys)
System Language: pt_BR.UTF-8
I know, looks like a simple deal, but this change of experience can be
problematic for some users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1235105/+subscriptions