FM / compat

/usr/share/X11/xkb/compat

Name	Size	Mode	Actions
accessx	1121	0644	edit dl rm
basic	1054	0644	edit dl rm
caps	507	0644	edit dl rm
complete	228	0644	edit dl rm
iso9995	1644	0644	edit dl rm
japan	986	0644	edit dl rm
ledcaps	469	0644	edit dl rm
lednum	466	0644	edit dl rm
ledscroll	486	0644	edit dl rm
level5	1396	0644	edit dl rm
misc	2724	0644	edit dl rm
mousekeys	4604	0644	edit dl rm
olpc	1133	0644	edit dl rm
pc	340	0644	edit dl rm
pc98	1226	0644	edit dl rm
README	1712	0644	edit dl rm
xfree86	1842	0644	edit dl rm
xtest	1457	0644	edit dl rm

Edit: /usr/share/X11/xkb/compat/README (1712B)

XKB maintains three compatibility state components that are used to make
XKB-unaware clients(*) work as well as possible:
- The compatibility state which corresponds to the effective modifier and
  effective group state.
- The compatibility lookup state which is the core-protocol equivalent of the
  lookup state.
- The compatibility grab state which is the nearest core-protocol equivalent
  of the grab state.

Compatibility states are essentially the corresponding XKB states, but with
the keyboard group possibly encoded as one or more modifiers.

Modifiers that correspond to each keyboard group are described in this
group compatibility map.

----
(*) The implementation of XKB invisibly extends the X library to use the
keyboard extension if it is present. That means, clients that use library or
toolkit routines to interpret keyboard events automatically use all of XKB's
features; clients that directly interpret the state field of core-protocol
events or the keymap directly may be affected by some of the XKB differences.
Thus most clients can take all advantages without modification but it also
means that XKB state can be reported to clients that have not explicitly
requested the keyboard extension.

The core protocol interpretation of keyboard modifiers does not include direct support for multiple keyboard groups, so XKB reports the effective keyboard group to XKB-aware clients using some of the reserved bits in the state field of some core protocol events. This modified state field would not be interpreted correctly by XKB-unaware clients, so XKB provides a group compatibility mapping which remaps the keyboard group into a core modifier mask that has similar effects, when possible. XKB maintains three compatibility state components that are used to make XKB-unaware clients(*) work as well as possible: - The compatibility state which corresponds to the effective modifier and effective group state. - The compatibility lookup state which is the core-protocol equivalent of the lookup state. - The compatibility grab state which is the nearest core-protocol equivalent of the grab state. Compatibility states are essentially the corresponding XKB states, but with the keyboard group possibly encoded as one or more modifiers. Modifiers that correspond to each keyboard group are described in this group compatibility map. ---- (*) The implementation of XKB invisibly extends the X library to use the keyboard extension if it is present. That means, clients that use library or toolkit routines to interpret keyboard events automatically use all of XKB's features; clients that directly interpret the state field of core-protocol events or the keymap directly may be affected by some of the XKB differences. Thus most clients can take all advantages without modification but it also means that XKB state can be reported to clients that have not explicitly requested the keyboard extension.