From: Andries Brouwer <aebr@win.tue.nl>
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org, John Bradford <john@grabjohn.com>
Subject: Re: 2.6.0-test5 vs. Japanese keyboards
Date: Tue, 23 Sep 2003 19:22:06 +0200 [thread overview]
Message-ID: <20030923192206.A1504@pclin040.win.tue.nl> (raw)
In-Reply-To: <145601c381c8$07956760$44ee4ca5@DIAMONDLX60>; from ndiamond@wta.att.ne.jp on Tue, Sep 23, 2003 at 08:44:12PM +0900
> > > > I think no kernel changes are required to use Japanese keyboards
> > > > today.
> > > > (But kbd has to be recompiled with NR_KEYS set to 256.)
> > >
> > > I'm not convinced yet. defkeymap.c_shipped is included in the
> > > downloadable .bz2 file and it is inadequate.
> >
> > But defkeymap is inadequeate for German, it is inadequate for French,
> > why would it be adequate for Japanese?
>
> I think that if defkeymap.c_shipped were inadequate for German and French
> then you already would have fixed it. I don't have experience with those
> keyboards but would guess that defkeymap.c_shipped is probably adequate for
> loadkeys to load a working keymap for German or French.
Of course. It is also adequate for loadkeys to load a working keymap
for Japanese.
> In order to be capable of loading a working keymap, defkeymap.c_shipped
> needs patching.
No.
> > It is just the random default you get when no keymap was loaded.
>
> It is that plus more. It includes limits that prevent certain keymaps from
> getting set when loaded.
False.
Andries
next prev parent reply other threads:[~2003-09-23 17:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 3:51 Norman Diamond
2003-09-14 10:20 ` 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 [this message]
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=20030923192206.A1504@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®