From: ryutaroh@it.ss.titech.ac.jp
To: john@grabjohn.com
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cannot input bar with JP106 keyboards
Date: Mon, 22 Dec 2003 10:59:29 +0900 (JST) [thread overview]
Message-ID: <20031222.105929.41650224.ryutaroh@it.ss.titech.ac.jp> (raw)
In-Reply-To: <200312201246.hBKCkP4a000191@81-2-122-30.bradfords.org.uk>
Hi John,
Thank you for your comments.
I agree to your description of keyboards and character sets.
From: John Bradford <john@grabjohn.com>
> > Is the change of keycode of upper-right backslash a new feature of
> > Linux 2.6? What is the advantage of this new feature?
>
> The placement of some keys seems to have changed over time. For
> example, tilde was once shift-0, whilst shift-caret was once overbar.
> My keyboard is marked in this way, and I am used to using shift-0 for
> tilde, however, shift-caret is apparently now popular as tilde, with
> shift-0 producing nothing.
>
> Backslash and Yen share the same code in 8-bit variations of
> ASCII-based. Therefore, the lower-right backslash key and the
> upper-right Yen key may in some cases be used interchangably.
(deleted)
But I haven't completely understand why the keycode of yen-"solid
vertical line" was changed.
(1) Backslash-underscore key (scancode 0x73) and yen-"solid vertical
line" key (scancode 0x7d) were given different keycodes (89 and
124) in Linux 2.4 . Do we have to change the keycode of yen-"solid
vertical line" key (scancode 0x7d) in Linux 2.6?
(2) I don't see why the new keycode is 183. Yen in Unicode is 165.
(3) The topic is keycode of the key having scancode 0x7d. In my
understanding, the assignment of keycodes has little to do with
what is printed on key top. Key tops are taken care by keymaps
loaded by loadkeys(1).
(4) Are there other keyboards having the key with scancode 0x7d? If
there are keyboards with scancode 0x7d in other languages, we
should take them into account.
Ryutaroh
next prev parent reply other threads:[~2003-12-22 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 12:24 ryutaroh
2003-12-19 12:36 ` Vojtech Pavlik
2003-12-20 9:30 ` ryutaroh
2003-12-20 9:35 ` Vojtech Pavlik
2003-12-20 9:52 ` ryutaroh
2003-12-20 12:46 ` John Bradford
2003-12-21 11:23 ` Jamie Lokier
2003-12-21 14:36 ` John Bradford
2003-12-22 1:59 ` ryutaroh [this message]
[not found] ` <fa.kfih9j0.q4e8bi@ifi.uio.no>
2003-12-23 20:58 ` Junio C Hamano
2003-12-24 1:28 ` ryutaroh
2003-12-21 11:07 Norman Diamond
2003-12-21 14:23 ` John Bradford
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=20031222.105929.41650224.ryutaroh@it.ss.titech.ac.jp \
--to=ryutaroh@it.ss.titech.ac.jp \
--cc=john@grabjohn.com \
--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 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®