Contents of /sourceforge.net/trunk/rdesktop/keymaps/README

Keymap-files
============
The keymaps are line based. There are three different types of lines:

1) include-lines
Syntax:
include <another-map-file>


2) map-lines
Syntax:
map <hex-number>

Map-lines specifies how the remote RDP server should interpret the
sent scancodes. 


3) Translation-lines
Syntax:
<keysym-name> <scancode> [flags..]

The scancode can be found in scancodes.h. Note: The scancode value for
extended keys can be calculated by OR:ing with 0x80. Example: The
Delete key have the scancode sequence 0xe0, 0x52. You can get the
scancode value to put into the map file by running:

python -c "print hex(0x80 | 0x52)"

If flags are "altgr", "shift", "numlock", the scancode sent for this
keysym will be prefix with AltGr, Shift or Numlock. 

If flags include "addupper", an translation for this keysyms uppercase
name will as well, in addition to the non-uppercase name. Example:

x 2d addupper

...will add an translation for "X" automatically, just like if you
would specify:

X 2d shift


Suggested X11 keysym mapping on PCs
===================================
Unfortunately, there is no standard for which keysyms a given key
should generate. If you have a PC-keyboard with Windows keys, I suggest this mapping:

Keyboard keys:
CtrlLeft WinLeft AltLeft Space AltGr WinRight Menu CtrlRight

...should generate keysyms:
Control_L Hyper_L Alt_L space Mode_switch Hyper_R Menu Control_R

Additionally:
Shift-Alt should produce Meta_L
Shift-AltGr should produce Multi_Key. 

Use a modifier-map like this:

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x25)
control     Control_L (0x42),  Control_R (0x6d)
mod1        Alt_L (0x40)
mod2        Num_Lock (0x4d)
mod3        Mode_switch (0x71)
mod4        Hyper_L (0x73),  Hyper_R (0x74)
mod5        Scroll_Lock (0x4e)
1	Keymap-files
2	============
3	The keymaps are line based. There are three different types of lines:
4
5	1) include-lines
6	Syntax:
7	include <another-map-file>
8
9
10	2) map-lines
11	Syntax:
12	map <hex-number>
13
14	Map-lines specifies how the remote RDP server should interpret the
15	sent scancodes.
16
17
18	3) Translation-lines
19	Syntax:
20	<keysym-name> <scancode> [flags..]
21
22	The scancode can be found in scancodes.h. Note: The scancode value for
23	extended keys can be calculated by OR:ing with 0x80. Example: The
24	Delete key have the scancode sequence 0xe0, 0x52. You can get the
25	scancode value to put into the map file by running:
26
27	python -c "print hex(0x80 \| 0x52)"
28
29	If flags are "altgr", "shift", "numlock", the scancode sent for this
30	keysym will be prefix with AltGr, Shift or Numlock.
31
32	If flags include "addupper", an translation for this keysyms uppercase
33	name will as well, in addition to the non-uppercase name. Example:
34
35	x 2d addupper
36
37	...will add an translation for "X" automatically, just like if you
38	would specify:
39
40	X 2d shift
41
42
43	Suggested X11 keysym mapping on PCs
44	===================================
45	Unfortunately, there is no standard for which keysyms a given key
46	should generate. If you have a PC-keyboard with Windows keys, I suggest this mapping:
47
48	Keyboard keys:
49	CtrlLeft WinLeft AltLeft Space AltGr WinRight Menu CtrlRight
50
51	...should generate keysyms:
52	Control_L Hyper_L Alt_L space Mode_switch Hyper_R Menu Control_R
53
54	Additionally:
55	Shift-Alt should produce Meta_L
56	Shift-AltGr should produce Multi_Key.
57
58	Use a modifier-map like this:
59
60	shift Shift_L (0x32), Shift_R (0x3e)
61	lock Caps_Lock (0x25)
62	control Control_L (0x42), Control_R (0x6d)
63	mod1 Alt_L (0x40)
64	mod2 Num_Lock (0x4d)
65	mod3 Mode_switch (0x71)
66	mod4 Hyper_L (0x73), Hyper_R (0x74)
67	mod5 Scroll_Lock (0x4e)