archive mirror
 help / color / mirror / Atom feed
From: John Bradford <>
Subject: Re: Japanese keyboards broken in 2.6
Date: Fri, 25 Jul 2003 17:39:11 +0100	[thread overview]
Message-ID: <> (raw)

> > > 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?
> Sorry - I am unable to make sense of your question.

The reason I mentioned it is because I've got a keyboard which
physically has a Japanese layout, but emulates a US keyboard in set 2.

Some keys which are shifted on a US keyboard, are not shifted on a
Japanese keyboard, for example, the colon key.  Presing colon on my
keyboard in set 2, causes it to send shift-; on the wire.  In set 3,
it sends the single code for the colon key.

I wondered whether some users in this thread had keyboards like mine,
which seem to produce unusual results when you analyse the scancodes
coming from them.  It looks like mine is rarer than I thought :-).

> Below some remarks, maybe related.
> Some remarks on scancode sets live on
> Not all keyboards support all scancode sets. For example,
> my MyCom laptop only supports scancode Set 2, and its keyboard
> does not react at all when in mode 1 or 3. 
> The normal, default mode is translated scancode set 2.
> Putting keyboards in other modes is asking for trouble.

Agreed.  Unfortunately, it's impossible to use some of the keys in set
2 on mine :-).


             reply	other threads:[~2003-07-25 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 16:39 John Bradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-25 16:01 Japanese keyboards broken in 2.6 John Bradford
2003-07-25 16:09 ` Andries Brouwer
2003-07-25  9:27 John Bradford
     [not found] <>
     [not found] ` <>
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

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:

* 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).