From: "Chris K. Jester-Young" <cky944@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Dvorak keymap for qemu
Date: Sat, 8 Aug 2009 21:56:59 -0400 [thread overview]
Message-ID: <20090809015659.GA26648@kettle> (raw)
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hi there,
I've noticed that the qemu distribution doesn't include a Dvorak
keymap, which means for people who connect to a qemu VNC session
from a computer using Dvorak, all the keys will be garbled.
Attached is a file which provides Dvorak keymap support. It's named
"en-dv" in line with how it's named in rdesktop (which, as mentioned
in the qemu source, was the basis of the keymaps support); however,
because I didn't know of rdesktop's version at the time I wrote the
keymap, my implementation is completely different.
I would appreciate it very much if either this file, or rdesktop's
version, could be integrated into the qemu tree.
Many thanks,
Chris.
[-- Attachment #2: en-dv --]
[-- Type: text/plain, Size: 811 bytes --]
include en-us
map 0x10409
# row 0
bracketleft 0x0c
braceleft 0x0c shift
bracketright 0x0d
braceright 0x0d shift
# row 1
apostrophe 0x10
quotedbl 0x10 shift
comma 0x11
less 0x11 shift
period 0x12
greater 0x12 shift
p 0x13 addupper
y 0x14 addupper
f 0x15 addupper
g 0x16 addupper
c 0x17 addupper
r 0x18 addupper
l 0x19 addupper
slash 0x1a
question 0x1a shift
equal 0x1b
plus 0x1b shift
# backslash 0x2b
# bar 0x2b shift
# row 2
# a 0x1e addupper
o 0x1f addupper
e 0x20 addupper
u 0x21 addupper
i 0x22 addupper
d 0x23 addupper
h 0x24 addupper
t 0x25 addupper
n 0x26 addupper
s 0x27 addupper
minus 0x28
underscore 0x28 shift
# row 3
semicolon 0x2c
colon 0x2c shift
q 0x2d addupper
j 0x2e addupper
k 0x2f addupper
x 0x30 addupper
b 0x31 addupper
# m 0x32 addupper
w 0x33 addupper
v 0x34 addupper
z 0x35 addupper
reply other threads:[~2009-08-09 1:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090809015659.GA26648@kettle \
--to=cky944@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.