summaryrefslogtreecommitdiff
path: root/README.enhancing
diff options
context:
space:
mode:
authorKevin E Martin <kem@kem.org>2005-02-08 00:44:27 +0000
committerKevin E Martin <kem@kem.org>2005-02-08 00:44:27 +0000
commiteb89db7b4da1533b5649a8ad67d5c24054984abe (patch)
treecd742720eebe89d0bfd2528ca627b9236258ec67 /README.enhancing
parentdb25ed8c0e57922d84e14f4885f110b7f74abc68 (diff)
Update formatted docs.XORG-6_8_2
Diffstat (limited to 'README.enhancing')
-rw-r--r--README.enhancing14
1 files changed, 7 insertions, 7 deletions
diff --git a/README.enhancing b/README.enhancing
index a8456e8..e1e64fc 100644
--- a/README.enhancing
+++ b/README.enhancing
@@ -132,12 +132,12 @@ comfortable to add one additional XKB term - group. You can think of a group
as of a vector of columns per each keycode (naturally the dimension of this
vector may differ for different keycodes). What is it good for? The group is
not very useful unless you intend to use more than one logically different
-set of symbols (like more than one alphabet) defined in a single mapping
-table. But then, the group has a natural meaning - each symbol set has its
-own group and changing it means selecting a different one. XKB approach
-allows up to four different groups. The columns inside each group are called
-(shift) levels. The X server knows the current group and reports it together
-with modifier set and with a keycode in key events.
+set of symbols (like more than one alphabet) defined in a single mapping ta-
+ble. But then, the group has a natural meaning - each symbol set has its own
+group and changing it means selecting a different one. XKB approach allows
+up to four different groups. The columns inside each group are called (shift)
+levels. The X server knows the current group and reports it together with
+modifier set and with a keycode in key events.
To sum it up:
@@ -506,4 +506,4 @@ rules file described above the .lst file could look like:
And that should be it. Enjoy creating your own xkb mapping.
-$XdotOrg$
+$XdotOrg: $