Hello there, I did not understand what to do in the section Configuring. I did missunderstand, by only reading the guide, that I had to modify files to make my own keyboard layout and not that the layout config info 'de' (or someone uses) is moved to the fdi file. It would be cool if the guide could be more detailed. I.e. refering to change Keyboard entries from: (I took the Example from the Xorg config guide) Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "be" EndSection to ( I used here my minimalistic entries. I suggest that the same example should be similar to the one used in the xorg config guide.) Section "InputDevice" Identifier "Keyboard0" Driver "evdev" Option "Protocol" "evdev" Option "XkbModel" "evdev" EndSection Instead of writeing: "For example, if you just want a basic configuration for a non-US keyboard layout, copy the content of /usr/share/doc/hal-*/use-estonian-layout.fdi.bz2 into /etc/hal/fdi/policy/10-xinput-configuration.fdi (using bzcat) and edit it to match the keyboard layout you wish to use. " I'd say something alike: "None US keyboard Layout is now configured in the file /etc/hal/fdi/policy/10-xinput-configuration.fdi. For an example how to look, see the file /usr/share/doc/hal-*/use-estonian-layout.fdi.bz2 (using bzcat)" Hmm, well this still needs some love. Maybe it is just simpler to copy the estonian example into the guide. (which is faster to grasp) <?xml version="1.0" encoding="UTF-8"?> <!-- Section "InputDevice" Driver "evdev" Option "XkbLayout" "ee" EndSection --> <deviceinfo version="0.2"> <match key="info.capabilities" contains="input.keyboard"> <merge key="input.x11_options.XkbLayout" type="string">ee</merge> </match> </deviceinfo> Thanks if you could add something like that. It took me 30 mins to sort the missunderstandings out :). Have Fun! Legine Reproducible: Always
Since 1.8 we have the guide for using udev. Which is described quite clearly. Since we keep that 1.5 guide now only for history reasons it is not worth of updating it now. Thanks for the bug anyway.
