X Strike Force XFree86 SVN commit: r1823 - in trunk/debian: . local
Author: barbier
Date: 2004-09-17 17:53:50 -0500 (Fri, 17 Sep 2004)
New Revision: 1823
Modified:
trunk/debian/CHANGESETS
trunk/debian/changelog
trunk/debian/local/FAQ.xhtml
Log:
Add FAQ entry: My keyboard configuration worked with XFree86 4.2, why is
it messed up now?
Modified: trunk/debian/CHANGESETS
===================================================================
--- trunk/debian/CHANGESETS 2004-09-17 22:48:46 UTC (rev 1822)
+++ trunk/debian/CHANGESETS 2004-09-17 22:53:50 UTC (rev 1823)
@@ -43,4 +43,8 @@
+ rules/xfree86.{lst,xml}: Perform changes to synchronize these files.
1822
+Add FAQ entry: My keyboard configuration worked with XFree86 4.2, why is
+it messed up now?
+ 1823
+
vim:set ai et sts=4 sw=4 tw=80:
Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2004-09-17 22:48:46 UTC (rev 1822)
+++ trunk/debian/changelog 2004-09-17 22:53:50 UTC (rev 1823)
@@ -24,6 +24,10 @@
(Closes: #271259)
+ rules/xfree86.{lst,xml}: Perform changes to synchronize these files.
+ * Add FAQ entry: My keyboard configuration worked with XFree86 4.2,
+ why is it messed up now?
+ (Closes: #259740)
+
Changes by Branden Robinson:
* In the Xsession script, attempt to create a file of non-zero length in
Modified: trunk/debian/local/FAQ.xhtml
===================================================================
--- trunk/debian/local/FAQ.xhtml 2004-09-17 22:48:46 UTC (rev 1822)
+++ trunk/debian/local/FAQ.xhtml 2004-09-17 22:53:50 UTC (rev 1823)
@@ -150,6 +150,8 @@
my X session exiting abnormally?</a></li>
<li><a href="#radeondualhead">I'm having trouble getting dual-head support to
work on my ATI Radeon card. Can you help?</a></li>
+<li><a href="#xkbnewlayout">My keyboard configuration worked with XFree86 4.2,
+ why is it messed up now?</a></li>
</ul>
<h2><a href="#acknowledgements">Acknowledgements</a></h2>
@@ -2673,6 +2675,39 @@
class="other">MonitorLayout</code> line, but I can't think of a physical
mechanism for this actually happening.</p>
+<h3><a id="xkbnewlayout">My keyboard configuration worked with XFree86 4.2,
+ why is it messed up now?</a></h3>
+
+<p>In releases previous to XFree86 4.3, combining several keymaps was
+difficult because keymaps had to be defined for each position. For instance
+<code>us</code> keymap was defined on first, second and third position,
+and this should have been done for all keymaps.</p>
+
+<p>Keymap layouts have been revisited in XFree86 4.3, and new definitions
+can now be used in whatever order so that <code>us,ru</code> and
+<code>ru,us</code> use the same definitions. New definitions have been put
+into <code class="filespec">/etc/X11/xkb/symbols/pc/</code> and old ones are
+still available at the same place, ie. under the
+<code class="filespec">/etc/X11/xkb/symbols/</code> directory,</p>
+
+<p>Some keymaps have not been converted to the new layout for any reason,
+and thus can not be combined with other keymaps. They are listed into
+<code class="filespec">/etc/X11/xkb/rules/xfree86</code>. If you have
+trouble combining keymaps, check that you do not try to load a keymap
+listed there.</p>
+
+<p>Modifiers have also been affected by these major changes to make this
+system more modular. A consequence is that <em>fake keys</em> have been
+introduced in XKB data files for <code>Alt</code>, <code>Meta</code>,
+<code>Super</code> and <code>Hyper</code> modifiers.
+By default, <code>mod1</code> and <code>mod4<code> use these fake keys
+instead of real ones. XKB-aware applications can handle those fake
+keys, but several applications get confused and do no more recognize
+your keys as modifiers. Until these applications are fixed, you can
+bind keys explicitly with <code>altwin</code> options, e.g.
+<kbd>Option "altwin:super_win"</kbd> binds your logo keys to
+<code>Super</code> modifiers.</p>
+
<h2><a id="acknowledgements">Acknowledgements</a></h2>
<p>The author would like to thank Andreas Metzler, Guillem Jover, Ingo Saitz,
Reply to: