From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] azerty [french] keyboard support
Date: Tue, 6 Feb 2001 00:11:44 -0500 [thread overview]
Message-ID: <200102060511.AAA21802@augusta.math.psu.edu> (raw)
In-Reply-To: <038f01c08fa7$74fe30e0$0ab9c6d4@cybercable.fr>
In article <038f01c08fa7$74fe30e0$0ab9c6d4@cybercable.fr> you write:
>i was of that opinion, but that would mean 3 zillion different
>keyboard types which would increase manufacturing costs. all
>you they do (in general) is to stick the right set of keytops
>on and a scan-code/character table is set up to match the
>keytops. you have to do the translation anyway and a table
>lookup costs nothing. in general it's done by some black art.
>
>the fix charles sent me is small and elegant and should
>work for some subset of japanese keyboards i think. if i
>remember, some have a shift, left shift and right shift keys
>(ie. 4 potential characters on each key).
This is exactly the sort of thing I'm talking about; making
a table driven translation machine driven by a little language.
What I don't like is the hardcoded tables in devcons.c.
I'll go out on a limb and say that I'd rather not see it in
the kernel at all, though. Maybe a very basic kernel based
driver for basic I/O, but then hook into a user level program
to do all the real processing. kbdfs, anyway? :-)
>however, japanese is a more complicated case. what i've seen
>is that you have a piece of code that sorts the kanji you use
>on a frequency basis, you type the stem of the prononciation
>and cycle through them till you get the one you want.
Ouch, that seems cumbersome, to put it mildly. :-( No offense
to the Japanese members of 9fans, but I'm glad I don't have to
type the language. :-)
- Dan C.
next prev parent reply other threads:[~2001-02-06 5:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 14:44 jmk
2001-02-05 18:46 ` Dan Cross
2001-02-05 19:11 ` Boyd Roberts
2001-02-06 5:11 ` Dan Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-07 2:11 William Staniewicz
2001-02-06 20:52 Russ Cox
[not found] <rob@plan9.bell-labs.com>
2001-02-06 17:11 ` rob pike
2001-02-06 19:10 ` Scott Schwartz
2001-02-06 19:23 ` Dan Cross
2001-02-06 16:44 Richard Miller
2001-02-06 16:19 rob pike
2001-02-06 13:34 William Staniewicz
2001-02-06 11:15 forsyth
2001-02-06 2:05 okamoto
2001-02-06 2:13 ` Boyd Roberts
2001-02-06 11:02 ` Boyd Roberts
2001-02-06 17:01 ` Dan Cross
2001-02-06 14:57 ` Wladimir Mutel
2001-02-06 18:34 ` Theo Honohan
2001-02-09 16:49 ` Boyd Roberts
2001-02-06 5:53 ` Dan Cross
2001-02-06 1:33 okamoto
2001-02-06 1:41 ` Boyd Roberts
2001-02-06 1:15 okamoto
2001-02-06 1:19 ` Boyd Roberts
2001-02-06 5:50 ` Dan Cross
2001-02-05 19:23 Ed Wishart
2001-02-06 5:20 ` Dan Cross
2001-02-05 18:55 jmk
2001-02-05 10:34 Boyd Roberts
2001-02-05 13:07 ` paurea
2001-02-05 13:15 ` Boyd Roberts
2001-02-05 18:44 ` Dan Cross
2001-02-05 8:05 anothy
2001-02-05 18:36 ` Dan Cross
2001-02-05 7:51 Jean Mehat
2001-02-05 1:33 okamoto
2001-02-05 1:40 ` Boyd Roberts
2001-02-04 0:55 rob pike
2001-02-04 1:09 ` Boyd Roberts
2001-02-04 4:29 ` Fariborz 'Skip' Tavakkolian
2001-02-04 13:28 ` Boyd Roberts
2001-02-04 14:09 ` Boyd Roberts
2001-02-05 5:59 ` Dan Cross
2001-02-04 0:54 rob pike
2001-02-04 1:19 ` Boyd Roberts
2001-02-04 1:23 ` andrey mirtchovski
2001-02-04 1:37 ` Boyd Roberts
2001-02-03 23:40 Boyd Roberts
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=200102060511.AAA21802@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).