From: John Bradford <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org
Cc: email@example.com, firstname.lastname@example.org
Subject: Re: Japanese keyboards broken in 2.6
Date: Fri, 25 Jul 2003 17:01:40 +0100 [thread overview]
Message-ID: <200307251601.h6PG1etD001373@81-2-122-30.bradfords.org.uk> (raw)
> > > setkeycodes 0x6a 124 1>&2 in your rc.local, local.start or whatever.
> > > works fine for me for alle 2.5x kernels
> > There must be a ton of odd stuff going on. "showkey" used to say that the
> > scan code is 0x7d not 0x6a, but now it displays weird stuff. As previously
> > mentioned, "getkeycodes" displays a table which seems far removed from
> > reality. But the patch from email@example.com worked (but "showkey" and
> > "getkeycodes" still produce weird output).
> I am a little bit unhappy with the state of the kbd code
> (but have not yet decided whether I want to attempt to fix something).
> One aspect of the matter is that raw mode no longer is raw.
> The keyboard sends codes and the input layer translates that into
> the codes the input layer thinks the keyboard should have sent.
> Then, when one wants the raw codes, a reverse translation is used,
> but since the mapping is not one-to-one the reverse translation
> does not produce what the keyboard sent to start with.
Doesn't AT-set3 usually have a closer one to one mapping of keys?
next reply other threads:[~2003-07-25 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 16:01 John Bradford [this message]
2003-07-25 16:09 ` Japanese keyboards broken in 2.6 Andries Brouwer
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 16:39 John Bradford
2003-07-25 9:27 John Bradford
[not found] <firstname.lastname@example.org>
[not found] ` <email@example.com>
2003-07-25 1:00 ` junkio
2003-07-25 4:16 ` OGAWA Hirofumi
2003-07-22 13:56 Norman Diamond
2003-07-22 15:29 ` Andries Brouwer
2003-07-23 13:14 ` Norman Diamond
2003-07-23 13:38 ` OGAWA Hirofumi
2003-07-24 11:16 ` Hiroshi Miura
2003-07-24 14:26 ` OGAWA Hirofumi
2003-07-25 7:49 ` Clemens Schwaighofer
2003-07-25 10:30 ` Norman Diamond
2003-07-25 15:42 ` Andries Brouwer
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).