Keymaps are a dense stream of keysym_t:

POS <CMD> NORMAL <SHIFT> <ALTGR> <SHIFT-ALTGR> where

POS (always KC(pos)) starts the description of a key `pos'.
CMD is the optional command if command modifier is in use (must be KS_Cmd_XXX).
NORMAL is the keysym if no modifiers are pressed.
SHIFT is the keysym if shift modifier is in use.
ALTGR and SHIFT-ALTGR are the keysyms if alt-gr modifier in use.

If the keysym after POS is not KS_Cmd_XXX, the command field is empty.
SHIFT, ALTGR and SHIFT-ALTGR are determined from previous fields if empty.

So there are four cases:

POS <CMD> NORMAL
POS <CMD> NORMAL SHIFT
POS <CMD> NORMAL SHIFT ALTGR
POS <CMD> NORMAL SHIFT ALTGR SHIFT-ALTGR

where the missing fields are determined from previous fields.

> 
> In message <Pine.NEB.4.40.0112151814140.17665-100000@yerfable.azeotrope.org>, D
> ave Huang writes:
> >In case anyone wants to come up with some nice wscons or xmodmap
> >mappings for the IA-1's wireless keyboard, here are the keycodes for the
> >special keys:
> 
> Excellent!  Can someone explain how the wskbd stuff works?  I am totally
> stumped by a file that, so far as I can tell, consists of purely magical
> structures where writing
> /* pos		command		normal		shifted */
> and following it with arbitrary subsets of those columns, with nothing in
> the unused columns, magically works.
> 
> I'd like to add a standard keyboard config for this, ala IOPENER.  Thinking
> of using the print->escape thing, setting the standard escape to become
> some kind of shift, and then binding the top keys to the functions.  I do
> like the forward/back buttons, and would sort of like to bind them to
> alt-left-arrow and alt-right-arrow.  ;)
> 
> -s
> 


-- 
Juergen Hannken-Illjes - hannken@eis.cs.tu-bs.de - TU Braunschweig (Germany)