Sun Keyboard Mapping
  by Glenn Everhart
The following inputs to xmodmap can be used before a call to xterm
on the Suns. They accomplish the following keyboard mapping:
1. PF1 to PF4 become the R4 to R6 keys and the keypad - key
(i.e., same positions they have on a vt100 keypad)
2. the keypad 0 adn . and enter keys work as on a VT100/VT200
3. The keypad arrow keys are the arrow keys.
4. Keypad 1 to 9 on a VT100 become F2 to F10 on the Sun; that
is, the F key just above the number key is the correct one.
5. F12 is the VT100 keypad - key and the Sun keypad + key is
the VT100 keypad + key.
6. The Sun keypad 9 and 3 keys (PgUp and PgDn) become the VT200
series Prev Screen and Next Screen keys.
7. The R1 through R3 keys become VT200 keypad F17 to F19 keys.
   These mappings can be gotten used to (I'm not so sure about the
SUN keyboard that drops duplicate characters unless one types SLOWLY)
and give the ability to use all of SEDT or EDT. One gets key names
from some of the openwindow .h files (key*.h) in case one wants to
extend this. The xev application shows keycodes.
------------ cut here -----------------
keycode 52 = KP_F1
keycode 53 = KP_F2
keycode 54 = KP_F3
keycode 78 = KP_F4
keycode 18 = KP_Subtract
keycode 132 = KP_Separator
keycode 13 = KP_1
keycode 15 = KP_2
keycode 17 = KP_3
keycode 19 = KP_4
keycode 21 = KP_5
keycode 23 = KP_6
keycode 24 = KP_7
keycode 25 = KP_8
keycode 14 = KP_9
keycode 101 = KP_0
keycode 57 = KP_Decimal
keycode 77 = Prior
keycode 121 = Next
keycode 125 = Help
keycode 28 = F17
keycode 29 = F18
keycode 30 = F19

