All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <linux-kernel@vger.kernel.org>
Cc: "Vojtech Pavlik" <vojtech@suse.cz>
Subject: 2.6.0-test5 vs. Japanese keyboards
Date: Sun, 14 Sep 2003 12:51:32 +0900	[thread overview]
Message-ID: <1b7301c37a73$861bea70$2dee4ca5@DIAMONDLX60> (raw)

In thread "Re: Trying to run 2.6.0-test3", Alan Cox replied to me:

> > What will it take this time?
>
> Posting the patch with any luck ?

I knew that that would not be sufficient.  On 2003.07.24, I think in the
days of 2.6.0-test1, junkio@cox.net posted a patch for Japanese PS/2
keyboards.  On 2003.08.31, in the days of 2.6.0-test4, I posted a revised
patch to include Japanese USB keyboards.  2.6.0-test5 includes neither of
them because the keyboard driver maintainers don't personally depend on
Japanese keyboards.

Since posting has not been sufficient, I beg Mr. Pavlik, just once per
release, please try pretending that you might have to depend on a Japanese
keyboard.  You don't have to use one daily as your colleague Dr. Fabian
does.  Just twice per release, once in a plain text console and once under
X11, please try testing a Japanese PS/2 keyboard and Japanese USB keyboard.

In particular the troublesome keys are yen bar and backslash underscore.
You don't need a Japanese font.  If you use an ASCII font then the keys
display as backslash bar and backslash underscore.  If you use a Japanese
font then the keys display as yen bar and yen underscore.  In all cases the
ASCII backslash or JIS-Romaji yen character are code point 0x5C.

(Don't worry about the labels on the right-hand side of each key, for direct
kana input.  Less than 0.1% of Japanese and other residents of Japan ever
use direct kana input under Monopolysoft Windows, and probably none at all
under Linux.  When inputting Japanese, common practice is to input the
pronunciation in Italian characters and let the OS convert first to kana and
then to Kanji.  We depend on the labels on the left-hand side of each key,
including the two mentioned above.  Exception 1:  yen and backslash are
really the same character even though the keys have different labels.
Exception 2:  a shifted 0 doesn't really produce a ~ but it is enough that a
shifted ^ does so, but it doesn't matter that Linux has added real input for
a shifted 0.)


             reply	other threads:[~2003-09-14  3:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-14  3:51 Norman Diamond [this message]
2003-09-14 10:20 ` 2.6.0-test5 vs. Japanese keyboards Andries Brouwer
2003-09-14 11:14   ` 2.6.0-test5 vs. Japanese keyboards [1] Norman Diamond
2003-09-14 11:15   ` 2.6.0-test5 vs. Japanese keyboards [2] Norman Diamond
2003-09-14 11:21   ` 2.6.0-test5 vs. Japanese keyboards [3] Norman Diamond
2003-09-16 13:43     ` Andries Brouwer
2003-09-17 12:35       ` OGAWA Hirofumi
2003-09-17 17:22         ` Andries Brouwer
2003-09-18 16:15           ` OGAWA Hirofumi
2003-09-21 11:06       ` Vojtech Pavlik
2003-09-21 12:39         ` Andries Brouwer
2003-09-21 12:48           ` Vojtech Pavlik
2003-09-21 14:49             ` Andries Brouwer
2003-09-21 17:07               ` Vojtech Pavlik
2003-09-21 17:42                 ` Andries Brouwer
2003-09-21 17:52                   ` Vojtech Pavlik
2003-09-22 12:22                 ` Norman Diamond
2003-09-24 10:02               ` Pavel Machek
     [not found]     ` <fa.gddv2je.1jk671u@ifi.uio.no>
2003-09-16 18:11       ` Junio C Hamano
2003-09-21 11:01 ` 2.6.0-test5 vs. Japanese keyboards Vojtech Pavlik
2003-09-21 13:26   ` Norman Diamond
2003-09-21 15:16     ` Andries Brouwer
2003-09-22 12:21       ` Norman Diamond
2003-09-22 20:14         ` Andries Brouwer
2003-09-23 11:44           ` Norman Diamond
2003-09-23 17:22             ` Andries Brouwer
2003-10-15 10:22               ` Norman Diamond
2003-09-21 16:00   ` Andries Brouwer
2003-09-21 12:00 John Bradford
2003-09-21 12:45 ` 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:
  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='1b7301c37a73$861bea70$2dee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.