From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: Re: [kbd] [PATCH] loadkeys: Auto-convert “traditional”/Unicode keysyms
Date: Thu, 16 Apr 2009 04:07:58 +0400 [thread overview]
Message-ID: <49E676DE.70200@gmail.com> (raw)
In-Reply-To: <20090415135344.GA3881@graeme>
15.04.2009 17:53, Michael Schutte wrote:
> Thanks for your testing, I completely missed this. But you can still
> type the affected characters, right? As far as I can tell, it’s only
> dumpkeys which is wrong here.
Your patch still does not work for me.
$ kbd_mode -a
$ export LANG=ru_RU.koi8r
$ setfont data/consolefonts/koi8r-8x16
# loadkeys data/keymaps/i386/qwerty/ruwin_cplk-KOI8-R.map
When typing characters are visible correctly.
But with your patch:
# src/loadkeys data/keymaps/i386/qwerty/ruwin_cplk-KOI8-R.map
When I typing the characters displayed incorrectly.
How do you test this patch?
Can you show how loadkeys with this patch to be used in the examples?
I'm not sure that understand this. Do you want to load 8-bit keymaps
for UTF locales and unicode keymaps for non-UTF locales ? Am i right ?
--
Rgrds, legion
next prev parent reply other threads:[~2009-04-16 0:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 17:45 [kbd] [PATCH] loadkeys: Auto-convert “traditional”/Unicode keysyms Michael Schutte
2009-04-14 21:37 ` Alexey Gladkov
2009-04-15 13:53 ` Michael Schutte
2009-04-16 0:07 ` Alexey Gladkov [this message]
2009-04-16 15:45 ` Michael Schutte
2009-04-16 23:01 ` Alexey Gladkov
2009-04-17 13:44 ` Alexey Gladkov
2009-04-17 20:01 ` Michael Schutte
2009-04-19 15:59 ` Alexey Gladkov
2009-04-19 16:50 ` Michael Schutte
2009-04-19 17:14 ` Alexey Gladkov
2009-04-20 18:39 ` Michael Schutte
2009-04-21 10:08 ` Alexey Gladkov
2009-04-21 13:20 ` Michael Schutte
2009-04-16 23:36 ` Alexey Gladkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E676DE.70200@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox