public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Jamie Lokier" <jamie@shareable.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Input issues - key down with no key up
Date: Mon, 25 Aug 2003 21:15:40 +0900	[thread overview]
Message-ID: <052a01c36b02$9de086f0$24ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20030825042414.GC20529@mail.jlokier.co.uk

"Jamie Lokier" <jamie@shareable.org> replied to me:

> > For Japanese versions of Windows 95 or 98 or NT4, of course the Japanese
> > keys do produce input.  Of course the Japanese layout driver is
> > involved.  I don't recall if the lower-level keyboard driver has a name
> > that distinguishes it from the US-101 driver, but the binaries are
> > almost certainly different.

[And for Japanese versions of Windows 2000 and Windows XP, of course the
Japanese keys do produce input.  Of course the Japanese layout driver is
involved, but also the lower-level driver is named for the Japanese-106
keyboard.]

> Do you know what the Japanese keys do under Linux?

I don't recall them doing anything under Linux.  I think I've read some
people say that the Japanese keys yield spaces for them, which would not be
too bad because three of those keys are next to the space bar anyway.  But I
think I get no input at all for them, which also isn't too bad (mostly -- 
but see below).

Of course the problem which is too bad is getting no input for the keys
yen-sign or-bar and backslash underscore.

In 2.4, after the USB-to-emulated-PS/2 translation level in the driver was
finally patched, I think that all of the Japanese keys were finally patched
to yield the same as the PS/2 translations of the USB keys.  The patch was
different from the one which I sent which was ignored, for which the
difference is OK (the effect is the same) but it really bugged me that it
was ignored for months.  Anyway, after the patch in 2.4, the potential of
letting the Japanese keys do something in Linux depended only on the
possibility of acting at the PS/2 layer or above.

In 2.6, I have a feeling that there might be one or two levels of breakage,
as there has been for the yen-sign or-bar and backslash underscore keys.
Sorry I neglected to test them two days ago.  But for that matter, the test
which I reported two days ago seems to have been ignored again.  I can only
volunteer about one day a week, but some people get paid to do this as their
job, and I wonder why my report has been ignored.

Now, I think I've read that ATOK can run under Linux.  Monopolysoft's IME is
based on ATOK's IME so a lot of people are used to it.  There are also other
IMEs under development for Linux.  For me and at least one other Usenetter
in Japan, it is a nuisance that Shift+Space turns on the X-11 IME, because
we often type it when we just want a space (if our thumb is still on the
Shift key from typing the previous character).  It really would be nice if
we could configure the hankaku/zenkaku key to turn the IME on or off the way
ATOK and Monopolysoft do, and then configure Shift+Space to just input a
Space.  But this would depend on making the Japanese keys do something in
Linux.  By the way the hankaku/zenkaku key is the one which isn't next to
the space bar, it's in the position which yields ` and ~ on a US keyboard.

(As for why the hankaku/zenkaku key turns the IME on and off instead of
switching between hankaku and zenkaku, the reason is yet another compound of
hacks, but people are used to it now.  Actually Alt+hankaku/zenkaku does
still also turn the IME on and off as it always did.  Except under Linux of
course.  I think it's still a no-op under Linux.)


  reply	other threads:[~2003-08-25 12:17 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 12:30 Input issues - key down with no key up Norman Diamond
2003-08-25  4:24 ` Jamie Lokier
2003-08-25 12:15   ` Norman Diamond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-25 12:47 John Bradford
2003-08-25  8:45 John Bradford
2003-08-21 12:11 John Bradford
2003-08-21 12:26 ` Vojtech Pavlik
2003-08-20  5:59 John Bradford
2003-08-20 15:17 ` Jamie Lokier
2003-08-19 19:37 John Bradford
2003-08-19 23:58 ` Jamie Lokier
2003-08-16 15:15 John Bradford
2003-08-18 11:53 ` Maciej W. Rozycki
2003-08-15  5:16 Neil Brown
2003-08-15  7:46 ` Andries Brouwer
2003-08-15 10:58   ` Vojtech Pavlik
2003-08-15 12:36     ` Andries Brouwer
2003-08-15 12:43       ` Vojtech Pavlik
2003-08-15 13:27         ` Jamie Lokier
2003-08-15 13:52           ` Vojtech Pavlik
2003-08-15 14:02             ` Jamie Lokier
2003-08-15 15:05         ` Jason Lunz
2003-08-15 13:04       ` Jamie Lokier
2003-08-15 13:10         ` Vojtech Pavlik
2003-08-15 13:33           ` Jamie Lokier
2003-08-15 13:53             ` Vojtech Pavlik
2003-08-16 13:02               ` Maciej W. Rozycki
2003-08-16 14:09                 ` Jamie Lokier
2003-08-17 21:54                   ` Vojtech Pavlik
2003-08-18 12:22                     ` Maciej W. Rozycki
2003-08-18 10:29                 ` Andries Brouwer
2003-08-19 13:04                   ` Maciej W. Rozycki
2003-08-19 17:48                     ` Andries Brouwer
2003-08-21 11:37                       ` Maciej W. Rozycki
2003-08-21 12:44                         ` Andries Brouwer
2003-08-21 13:45                           ` Maciej W. Rozycki
2003-08-21 14:28                             ` Andries Brouwer
2003-08-21 14:38                               ` Maciej W. Rozycki
2003-08-21 13:48                         ` Jamie Lokier
2003-08-21 14:08                           ` Maciej W. Rozycki
2003-08-21 14:14                             ` Vojtech Pavlik
2003-08-21 14:33                               ` Maciej W. Rozycki
2003-08-21 14:44                                 ` Andries Brouwer
2003-08-21 15:03                                   ` Maciej W. Rozycki
2003-08-21 15:29                                     ` Vojtech Pavlik
2003-08-16 13:01             ` Maciej W. Rozycki
2003-08-15 12:46     ` Neil Brown
2003-08-15 12:54       ` Vojtech Pavlik
2003-08-15 13:52       ` Andries Brouwer
2003-08-15 14:13         ` Vojtech Pavlik
2003-08-16  7:57           ` Neil Brown
2003-08-18 16:01             ` Vojtech Pavlik
2003-08-19 11:40               ` Neil Brown
2003-08-19 11:50                 ` Vojtech Pavlik
2003-08-19 23:59                   ` Neil Brown
2003-08-20 22:36             ` Andries Brouwer
2003-08-20 22:58               ` Jamie Lokier
2003-08-20 23:52                 ` Andries Brouwer
2003-08-21  0:03                   ` Jamie Lokier
2003-08-21  0:33                     ` Andries Brouwer
2003-08-21  1:36                       ` Jamie Lokier
2003-08-21  8:08                       ` Vojtech Pavlik
2003-08-21  8:06                     ` Vojtech Pavlik
2003-08-21 11:40                     ` Maciej W. Rozycki
2003-08-21 12:48                       ` Andries Brouwer
2003-08-21 13:22                         ` Jamie Lokier
2003-08-21 13:29                         ` Maciej W. Rozycki
2003-08-21  8:01                   ` Vojtech Pavlik
2003-08-22  0:27                     ` Andries Brouwer
2003-08-22  7:33                       ` Vojtech Pavlik
2003-08-25  4:22                         ` Jamie Lokier
2003-08-25  8:22                           ` Vojtech Pavlik
2003-08-25 19:36                             ` Jamie Lokier
2003-09-03  8:06                               ` Pavel Machek
2003-08-22 13:35                       ` Maciej W. Rozycki

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='052a01c36b02$9de086f0$24ee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.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