From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <00f401c146d4$512f7400$a2b9c6d4@SOMA>
From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
References: <20010926165615.047CB19A55@mail.cse.psu.edu> <005201c146ad$b5a301d0$a2b9c6d4@SOMA>
Subject: Re: [9fans] Foreign keyboard layout
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date: Wed, 26 Sep 2001 23:43:44 +0200
Topicbox-Message-UUID: f501230a-eac9-11e9-9e20-41e7f4b1d025

azerty support is advancing, but i'm now at the point
of a pc/kbd.c hack or re-write to get it support certain
latin1 chars and shift/alt/alt-gr to work right.

the problem, but i'll have to study the code, is that it
uses the 8th bit to indicate a shifted char and then a series
of chars in the bottom end of the latin1 codespace to indicate
shift/ctrl/alt/etc.

this is a big problem because the runes are overloaded 'cos
an azerty keyboard 'generates' stuff with the 8th bit set.

this is reminiscent of the way the bourne shell used the
8th bit to indicate quoting -- yuk, and that's before
we get to the sigsegv memory management ...

a quick hack would be to use the 16th bit, but that may
provoke exactly the same problem further down the track,
which i most certainly want to avoid.

i hope i don't have to read the unicode spec -- gag ...