Updating formatted docs.xo-6_7_0XORG-RELEASE-1-MERGEXORG-CYGWIN-MERGEXORG-6_7_0

CVt: Enter Log. Lines beginning with `CVS:' are removed automatically

1 files changed, 17 insertions, 19 deletions

diff --git a/README.config b/README.config
index 4dd4d2e..588c861 100644
--- a/README.config
+++ b/README.config
@@ -23,23 +23,23 @@ The easiest and the most natural way how to specify a keyboard mapping is to
 use rules component. As its name suggests it describes a number of general
 rules how to combine all bits and pieces into a valid and useful keyboard
 mapping. All you need to do is to select a suitable rules file and then to
-feed it with a few parameters that will adjust the keyboard behaviour to ful­
+feed it with a few parameters that will adjust the keyboard behaviour to ful-
 fill your needs.
 
 The parameters are:
 
-   · XkbRules - files of rules to be used for keyboard mapping composition
+   o XkbRules - files of rules to be used for keyboard mapping composition
 
-   · XkbModel - name of model of your keyboard type
+   o XkbModel - name of model of your keyboard type
 
-   · XkbLayout - layout(s) you intend to use
+   o XkbLayout - layout(s) you intend to use
 
-   · XkbVariant - variant(s) of layout you intend to use
+   o XkbVariant - variant(s) of layout you intend to use
 
-   · XkbOptions - extra xkb configuration options
+   o XkbOptions - extra xkb configuration options
 
 The proper rules file depends on your vendor. In reality, the commonest file
-of rules is xorg. For each rules file there is a description file named <ven­
+of rules is xorg. For each rules file there is a description file named <ven-
 dor-rules>.lst, for instance xorg.lst which is located in xkb configuration
 subdirectory rules (for example /etc/X11/xkb/rules).
 
@@ -147,17 +147,17 @@ occasions it may be needed, though. So how does it work?
 
 There are five basic components used to form a keyboard mapping:
 
-   · key codes - a translation of the scan codes produced by the keyboard
+   o key codes - a translation of the scan codes produced by the keyboard
      into a suitable symbolic form
 
-   · types - a specification of what various combinations of modifiers pro­
+   o types - a specification of what various combinations of modifiers pro-
      duce
 
-   · key symbols - a translation of symbolic key codes into actual symbols
+   o key symbols - a translation of symbolic key codes into actual symbols
 
-   · geometry - a description of physical keyboard geometry
+   o geometry - a description of physical keyboard geometry
 
-   · compatibility maps - a specification of what action should each key pro­
+   o compatibility maps - a specification of what action should each key pro-
      duce in order to preserve compatibility with XKB-unware clients
 
 3.2  Example Configuration
@@ -175,11 +175,11 @@ Look at the following example:
          Option "XkbCompat"   "basic+pc+iso9995"
      EndSection
 
-This configuration sets the standard X server default interpretation of key­
-board keycodes, sets the default modificator types. The symbol table is com­
+This configuration sets the standard X server default interpretation of key-
+board keycodes, sets the default modificator types. The symbol table is com-
 posed of extended US keyboard layout in its variant for pc keyboards with 104
 keys plus all keys for german layout are redefined respectively. Also the
-logical meaning of Caps-lock and Control keys is swapped.  The standard key­
+logical meaning of Caps-lock and Control keys is swapped.  The standard key-
 board geometry (physical look) is set to pc style keyboard with 104 keys. The
 compatibility map is set to allow basic shifting, to allow Alt keys to be
 interpreted and also to allow iso9995 group shifting.
@@ -188,11 +188,9 @@ interpreted and also to allow iso9995 group shifting.
 
 It is the formerly used way to configure xkb. The user included a special
 keymap file which specified the direct xkb configuration. This method has
-been obsoleted by previously described rules files which are far more flexi­
+been obsoleted by previously described rules files which are far more flexi-
 ble and allow simpler and more intuitive syntax. It is preserved merely for
 compatibility reasons. Avoid using it if it is possible.
 
-     $Id$
+     Generated from Id: XKB-Config.sgml,v 1.1.4.1.6.2 eich Exp $
 
-
-$XFree86$