9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <andrey@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard maps
Date: Tue, 14 May 2002 12:50:18 -0600	[thread overview]
Message-ID: <9dea1e64fe2ef5e3b9009e8dfcee600a@acl.lanl.gov> (raw)

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

here's a file for typinng in cyrillic, with the bulgarian keyboard
layout..  i've put the necessary changes to add it as the third
keyboard mapping, but i'm sure everyone on the list (who cares) is
able to do it by themselves, so no diff for any other files...

for those interested: bug or a feature?  the cyrillic characters in
p9's utf fonts lack a capital 'ъ'.  russian does not have it,
bulgarian does, even though we have only one word that starts with it
-- 'ъгъл', meaning 'angle'...

андрей

[-- Attachment #2: kbd_bg.c --]
[-- Type: text/plain, Size: 3325 bytes --]

/* bulgarian phonetic keyboard mapping. note the lack of capital 'ъ' */
#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_bg[] =
{
[0x00]	No,	0x1b,	'1',	'2',	'3',	'4',	'5',	'6',
[0x08]	'7',	'8',	'9',	'0',	'-',	'=',	'\b',	'\t',
[0x10]	'я',	'в,	'е',	'р',	'т',	'ъ',	'у',	'и',
[0x18]	'о',	'п',	'ш', 	'щ',	'\n',	Ctrl,	'а',	'с',
[0x20]	'д',	'ф',	'г',	'х',	'й',	'к',	'л',	';',
[0x28]	'\'',	'ч',	Shift,	'ю',	'з',	'ь',	'ц',	'ж',
[0x30]	'б',	'н',	'м',	',',	'.',	'/',	Shift,	'*',
[0x38]	Latin,	' ',	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,	No,
[0x78]	No,	View,	No,	Up,	No,	No,	No,	No,
};

Rune kbtabshift_bg[] =
{
[0x00]	No,	0x1b,	'!',	'@',	'#',	'$',	'%',	'^',
[0x08]	'&',	'*',	'(',	')',	'_',	'+',	'\b',	'\t',
[0x10]	'Я',	'В',	'Е',	'Р',	'Т',	'ъ',	'У',	'И',
[0x18]	'О',	'П',	'Ш',	'Щ',	'\n',	Ctrl,	'А',	'С',
[0x20]	'Д',	'Ф',	'Г',	'Х',	'Й',	'К',	'Л',	':',
[0x28]	'"',	'Ч',	Shift,	'Ю',	'З',	'ь',	'Ц',	'Ж',
[0x30]	'Б',	'Н',	'М',	'<',	'>',	'?',	Shift,	'*',
[0x38]	Latin,	' ',	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,	No,
[0x78]	No,	Up,	No,	Up,	No,	No,	No,	No,
};

Rune kbtabesc1_bg[] =
{
[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]	Latin,	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_bg[] =
{
[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]	Latin,	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,
};--upas-twknbbkoeqbzexbchfjdczjqva--

             reply	other threads:[~2002-05-14 18:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14 18:50 andrey mirtchovski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-01 21:48 Heiko Dudzus
2005-11-01 22:34 ` Russ Cox
2005-11-02 19:49   ` Heiko Dudzus
2004-03-16 14:31 David Presotto
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
2002-05-20  9:55 Joel Salomon
2002-05-21  8:47 ` Joel Salomon
2002-05-16 13:18 rob pike, esq.
2002-05-16 11:06 nigel
2002-05-16 10:00 Fco.J.Ballesteros
2002-05-14 21:36 rob pike, esq.
2002-05-14 20:15 rob pike, esq.
2002-05-14 19:40 andrey mirtchovski
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
2002-05-18 19:57     ` Pavel Mihaylov
2002-05-21 10:43       ` Boyd Roberts
2002-05-21 11:35         ` Pavel Mihaylov

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=9dea1e64fe2ef5e3b9009e8dfcee600a@acl.lanl.gov \
    --to=andrey@lanl.gov \
    --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).