From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] azerty [french] keyboard support
Date: Mon, 5 Feb 2001 13:44:00 -0500 [thread overview]
Message-ID: <200102051844.NAA18802@augusta.math.psu.edu> (raw)
In-Reply-To: <018901c08f5f$276e9ec0$0ab9c6d4@cybercable.fr>
In article <018901c08f5f$276e9ec0$0ab9c6d4@cybercable.fr> you write:
>> (Yeah, I'm ignoring the fact that in said Paris Internet
>> Cafe, you were probably using an OS that expected a French
>> keyboard....)
>
>no. the scan codes from pc keyboards do not change, just
>the keytops. then, the translation is done in s/w. you
>only really need a french keyboard if you want to type
>latin-1, a superset of ascii.
Oh, okay. Then I'll repeat my question to Rob, ``what, you didn't
have your happy hacking keyboard with you?'' :-)
I remember using a computer in Israel one time. My friend's father
asked me, ``can you take a look at my old computer? I want to fix
it up and give it to my daughter....'' ``Uhh, I don't really do
Windows, so, I don't know if I'd be much help....'' ``Of course you
would! Here, have a look.''
Well, the keyboard had mixed English/Hebrew keycaps, which threw me
off whenever I looked at it. Luckily, I touch-type most of the time,
so it wasn't that big of a deal. Windows 95 was the Israeli edition,
so all of the text, including dialogue boxes, was in Hebrew. I can't
read Hebrew. I had to have people read the contents of every text
window on the system and translate into English before I could do
anything.... It was disconcerting.
>i always liked the 5620 keyboard. the sony vaio's
>is pretty close to that (well my 505's is); touch,
>key size and shape.
There's got to be a better way to handle keyboards than all this
magic in the kernel....
- Dan C.
next prev parent reply other threads:[~2001-02-05 18:44 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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 14:44 jmk
2001-02-05 18:46 ` Dan Cross
2001-02-05 19:11 ` Boyd Roberts
2001-02-06 5:11 ` 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=200102051844.NAA18802@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).