Specifications

CHAPTER 8 Configuring Devices
313
• xkeymap.language = <keyboard-type>
Use this if GSX Server has a table in xkeymap for your keyboard but can’t detect
it. <keyboard-type> must be one of the tables in the xkeymap directory.
(See above for location.) However, the failure to detect the keyboard probably
means the table isn’t completely correct for you.
• xkeymap.keysym.<sym> = <v-scan code>
If you use keysym mapping, map keysym <sym> to <v-scan code>. When
you do, <sym> must be an X keysym name and <v-scan code> should be a
C-syntax hexadecimal number (for example, 0x001).
The easiest way to find the keysym name for a key is to run xev or
xmodmap -pk.
The X header file /usr/X11R6/include/X11/keysymdef.h has a
complete list of keysyms. (The name of a keysym is the same as its C constant
without the XK_ prefix.) Most v-scan codes are in the V-Scan Code Table on
page 314.
The xkeymap tables themselves are also helpful. Use them to fix small errors in
an existing mapping.
• xkeymap.fileName = <file-path>
Use the keysym mapping table in <file-path>. A table is a sequence of
configuration lines of the form
<sym> = <v-scan code>
where <sym> is an X keysym name, and <v-scan code> is a C-syntax
hexadecimal number (for example, 0x001). (See the explanation of
xkeymap.keysym above for tips on finding the keysyms and v-scan codes for
your keyboard.)
Compiling a complete keysym mapping is difficult. It is best to start with an
existing table and make small changes.