9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Foreign keyboard layout
Date: Wed, 26 Sep 2001 23:10:18 +0100	[thread overview]
Message-ID: <20010926221608.7191B19A31@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 145 bytes --]

you can map Shift and some of the other special keys
elsewhere in the Unicode space; it's not quite like
the use of 0200 by the old shells.


[-- Attachment #2: Type: message/rfc822, Size: 2790 bytes --]

From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Foreign keyboard layout
Date: Wed, 26 Sep 2001 23:43:44 +0200
Message-ID: <00f401c146d4$512f7400$a2b9c6d4@SOMA>

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 ...


             reply	other threads:[~2001-09-26 22:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 22:10 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-27  1:05 Russ Cox
2001-09-27  1:06 ` Boyd Roberts
2001-09-29  2:44 ` Boyd Roberts
2001-09-29 20:49   ` Boyd Roberts
2001-09-30  2:20     ` Boyd Roberts
2001-09-26 22:45 Russ Cox
2001-09-26 22:48 ` Boyd Roberts
2001-09-26 22:58 ` Boyd Roberts
2001-09-26 17:08 rog
2001-09-26 17:07 ` Boyd Roberts
2001-09-26 21:43   ` Boyd Roberts
2001-09-24 17:47 forsyth
2001-09-24 17:56 ` Boyd Roberts
2001-09-24 16:58 forsyth
2001-09-24 17:21 ` Boyd Roberts
2001-09-26 16:41   ` Boyd Roberts
2001-09-18  7:02 Jesus A. Mora
2001-09-18 10:51 ` Boyd Roberts
2001-09-19 10:52   ` Jesus A. Mora
2001-09-19 12:49     ` Boyd Roberts
2001-09-19 16:52     ` Quinn Dunkan
2001-09-19 17:07       ` Boyd Roberts
2001-09-20  7:43       ` Jesus A. Mora

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=20010926221608.7191B19A31@mail.cse.psu.edu \
    --to=forsyth@caldo.demon.co.uk \
    --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).