From: arisawa@ar.aichi-u.ac.jp
To: 9fans@nx.aichi-u.ac.jp
Subject: [9fans] Japanese keyboard map
Date: Sat, 15 Jun 2002 11:33:51 +0900 [thread overview]
Message-ID: <20020615023359.4E8E81998C@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 142 bytes --]
Hello,
Japanese keyboard map is attached.
[An attachment was originally included here]
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
[-- Attachment #2.1.1: Type: text/plain, Size: 286 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: text/enriched; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
[-- Attachment #2.1.2: file.suspect --]
[-- Type: application/octet-stream, Size: 52 bytes --]
Hello,
Japanese keyboard map is attached.
[-- Attachment #2.2: kbd_jp.c --]
[-- Type: application/octet-stream, Size: 3085 bytes --]
#include "u.h"
#include "libc.h"
#include "kbd.h"
/*
* The codes at 0x79 and 0x81 are produed by the PFU Happy Hacking keyboard.
* A 'standard' keyboard doesn't produce anything above 0x58.
*/
Rune kbtab_jp[] =
{
[0x00] No, 0x1b, '1', '2', '3', '4', '5', '6',
[0x08] '7', '8', '9', '0', '-', '^', '\b', '\t',
[0x10] 'q', 'w', 'e', 'r', 't', 'y', 'u', 'i',
[0x18] 'o', 'p', '@', '[', '\n', Ctrl, 'a', 's',
[0x20] 'd', 'f', 'g', 'h', 'j', 'k', 'l', ';',
[0x28] ':', '`', Shift, ']', 'z', 'x', 'c', 'v',
[0x30] 'b', 'n', 'm', ',', '.', '/', Shift, '*',
[0x38] Compose, ' ', Ctrl, KF|1, KF|2, KF|3, KF|4, KF|5,
[0x40] KF|6, KF|7, KF|8, KF|9, KF|10, Num, Scroll, '7',
[0x48] '8', '9', '-', '4', '5', '6', '+', '1',
[0x50] '2', '3', '0', '.', No, No, No, KF|11,
[0x58] KF|12, No, No, No, No, No, No, No,
[0x60] No, No, No, No, No, No, No, No,
[0x68] No, No, No, No, No, No, No, No,
[0x70] No, No, No, '\\', No, No, No, No,
[0x78] No, View, No, Up, No, '¥', No, No,
};
Rune kbtabshift_jp[] =
{
[0x00] No, 0x1b, '!', '"', '#', '$', '%', '&',
[0x08] '\'', '(', ')', '~', '=', '~', '\b', '\t',
[0x10] 'Q', 'W', 'E', 'R', 'T', 'Y', 'U', 'I',
[0x18] 'O', 'P', '`', '{', '\n', Ctrl, 'A', 'S',
[0x20] 'D', 'F', 'G', 'H', 'J', 'K', 'L', '+',
[0x28] '*', '~', Shift, '}', 'Z', 'X', 'C', 'V',
[0x30] 'B', 'N', 'M', '<', '>', '?', Shift, '*',
[0x38] Compose, ' ', Ctrl, KF|1, KF|2, KF|3, KF|4, KF|5,
[0x40] KF|6, KF|7, KF|8, KF|9, KF|10, Num, Scroll, '7',
[0x48] '8', '9', '-', '4', '5', '6', '+', '1',
[0x50] '2', '3', '0', '.', No, No, No, KF|11,
[0x58] KF|12, No, No, No, No, No, No, No,
[0x60] No, No, No, No, No, No, No, No,
[0x68] No, No, No, No, No, No, No, No,
[0x70] No, No, No, '_', No, No, No, No,
[0x78] No, Up, No, Up, No, '|', No, No,
};
Rune kbtabesc1_jp[] =
{
[0x00] No, No, No, No, No, No, No, No,
[0x08] No, No, No, No, No, No, No, No,
[0x10] No, No, No, No, No, No, No, No,
[0x18] No, No, No, No, '\n', Ctrl, No, No,
[0x20] No, No, No, No, No, No, No, No,
[0x28] No, No, Shift, No, No, No, No, No,
[0x30] No, No, No, No, No, '/', No, Print,
[0x38] Compose, No, No, No, No, No, No, No,
[0x40] No, No, No, No, No, No, Break, Home,
[0x48] Up, Pgup, No, Left, No, Right, No, End,
[0x50] Down, Pgdown, Ins, Del, No, No, No, No,
[0x58] No, No, No, No, No, No, No, No,
[0x60] No, No, No, No, No, No, No, No,
[0x68] No, No, No, No, No, No, No, No,
[0x70] No, No, No, No, No, No, No, No,
[0x78] No, Up, No, No, No, No, No, No,
};
Rune kbtabalt_jp[] =
{
[0x00] No, No, No, No, No, No, No, No,
[0x08] No, No, No, No, No, No, No, No,
[0x10] No, No, No, No, No, No, No, No,
[0x18] No, No, No, No, No, No, No, No,
[0x20] No, No, No, No, No, No, No, No,
[0x28] No, No, No, No, No, No, No, No,
[0x30] No, No, No, No, No, No, No, No,
[0x38] Compose, No, No, No, No, No, No, No,
[0x40] No, No, No, No, No, No, No, No,
[0x48] No, No, No, No, No, No, No, No,
[0x50] No, No, No, No, No, No, No, No,
[0x58] No, No, No, No, No, No, No, No,
[0x60] No, No, No, No, No, No, No, No,
[0x68] No, No, No, No, No, No, No, No,
[0x70] No, No, No, No, No, No, No, No,
[0x78] No, No, No, No, No, No, No, No,
};
[-- Attachment #2.3.1: Type: text/plain, Size: 286 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: text/enriched; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
[-- Attachment #2.3.2: file.suspect --]
[-- Type: application/octet-stream, Size: 56 bytes --]
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~2002-06-15 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 2:33 arisawa [this message]
2002-06-15 15:24 ` FJ Ballesteros
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=20020615023359.4E8E81998C@mail.cse.psu.edu \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@nx.aichi-u.ac.jp \
/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).