From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] azerty [french] keyboard support
Date: Tue, 6 Feb 2001 11:19:18 -0500 [thread overview]
Message-ID: <20010206161917.96AF2199EA@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 203 bytes --]
What is the difference between unicode symbols 20A0 and 20AC?
Which should have which escape sequence? I'll put what's appropriate
in /lib/keyboard here but I'm not the right judge of that.
-rob
[-- Attachment #2: Type: message/rfc822, Size: 3519 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 310 bytes --]
i'd add a mapping e$ -> 20AC to /lib/keyboard and remake the kernel.
then alt e$ will produce the euro symbol as l$ produces pound sterling and
y$ produces yen.
interpreting plain alt e as euro would mess up existing mappings
because there are several alt escapes in /lib/keyboard
that start with e.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1710 bytes --]
From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] azerty [french] keyboard support
Date: Tue, 6 Feb 2001 08:34:03 -0500
Message-ID: <20010206073748.49391199EA@mail.cse.psu.edu>
I have been using an Italian keyboard for the last several
months. I am not concerned about remapping all the keys
since I now have gotten used to where everything is.
However, the is a Euro dollar key that I would like to
implement. Is there a simple way on Plan9 to assign this
symbol to my "e" <alt> position?
-Bill
next reply other threads:[~2001-02-06 16:19 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 16:19 rob pike [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 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 10:34 Boyd Roberts
2001-02-05 13:07 ` paurea
2001-02-05 13:15 ` Boyd Roberts
2001-02-05 18:44 ` 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=20010206161917.96AF2199EA@mail.cse.psu.edu \
--to=rob@plan9.bell-labs.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).