From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3CE383A5.F60D645B@strakt.com> From: Boyd Roberts MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] keyboard maps References: <2ddd507ce00ca87c2bcc7eb42e70c919@plan9.escet.urjc.es> <1021498469.3079.20.camel@dator> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 May 2002 12:02:13 +0200 Topicbox-Message-UUID: 9429056a-eaca-11e9-9e20-41e7f4b1d025 Pavel Mihaylov wrote: > In kbd.h Altgr is defined as 0x38 which disagrees with the other > shift-state keys (Shift, Ctrl, etc). This is apparently the reason to > use variable gr, needed to differentiate between Altgr and simply 0x38 > (which is actually '8'). IIRC this is so that the 'compose' keys on either side of the space bar do the same thing. On keyboards where Alg-Gr acts as a second 'shift' this is a bad idea. > I've changed the definition of Altgr to Spec|0x67 Yes that's right. I'd also change Spec too: Spec= 0xF800, /* Unicode private space */ Altgr= Spec|0x67, If Spec is 0x80 it causes all sorts of woe when you hit Latin-1 characters. > Btw, isn't it wise to rename Latin from kbd.h to something more meaningful, > such as Compose, since composing is used to enter much more than Roman-script > based characters? Sure would, as it is confusing and actually indicates the collection of a multi character sequence, which may not be related to 'latin' characters at all.