From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard maps
Date: Thu, 16 May 2002 12:02:13 +0200 [thread overview]
Message-ID: <3CE383A5.F60D645B@strakt.com> (raw)
In-Reply-To: <1021498469.3079.20.camel@dator>
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.
next prev parent reply other threads:[~2002-05-16 10:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 17:37 Fco.J.Ballesteros
2002-05-15 9:05 ` Boyd Roberts
2002-05-15 21:34 ` Pavel Mihaylov
2002-05-16 10:02 ` Boyd Roberts [this message]
2002-05-18 19:57 ` Pavel Mihaylov
2002-05-21 10:43 ` Boyd Roberts
2002-05-21 11:35 ` Pavel Mihaylov
2002-05-14 18:50 andrey mirtchovski
2002-05-14 19:40 andrey mirtchovski
2002-05-14 20:15 rob pike, esq.
2002-05-14 21:36 rob pike, esq.
2002-05-16 10:00 Fco.J.Ballesteros
2002-05-16 11:06 nigel
2002-05-16 13:18 rob pike, esq.
2002-05-20 9:55 Joel Salomon
2002-05-21 8:47 ` Joel Salomon
2003-11-17 18:24 Fco.J.Ballesteros
2003-11-17 18:34 ` ron minnich
2003-11-17 18:41 ` Fco.J.Ballesteros
2003-11-17 19:56 ` mirtchov
2003-11-18 8:13 ` Fco.J.Ballesteros
2004-03-16 14:31 David Presotto
2005-11-01 21:48 Heiko Dudzus
2005-11-01 22:34 ` Russ Cox
2005-11-02 19:49 ` Heiko Dudzus
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=3CE383A5.F60D645B@strakt.com \
--to=boyd@strakt.com \
--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).