Summary: | logicdit symbol definitions missing from /usr/X11R6/lib/X11/xkb configuration files | ||
---|---|---|---|
Product: | xorg | Reporter: | Jukka Palko <jpalko> |
Component: | Input/Keyboard | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | mharris, svu |
Version: | 6.7.0 | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jukka Palko
2004-05-22 01:45:05 UTC
Is this still relevant in X11R7.0 with xkbdata or xkeyboard-config? If so, someone should check the changes into CVS so it's included in the next release, however that would be much easier if the reporter would attach a unified diff (diff -u) to the bug report as a file attachment, which implements the necessary changes against the current source code (not the files installed on the system). HTH Personally have changed to a Logitech Media keyboard, which has not either had any sufficient definitions thus far on 6.8 xorg. Will 7.x have definitions in a way or another for my newer keyboard? :) That depends on wether or not someone who has one of those keyboards, spends the time to add support for their keyboard, creates a unified diff of their changes - against the sources, and submits a bug report with their patch attached. Support is generally added for any type of hardware, either when a vendor wants their hardware supported, or otherwise when someone does the work for themselves, so that their hardware is supported, and submits it properly. I can't imagine random X developers running out to buy one of every keyboard out there for example, just for the priveledge of trying to add support for them all. ;o) Volunteers? I'm quite willing to contribute my efforts as soon as I have time to install Xorg 7 on my gentoo. There is logicdit in xkeyboard-config. Since xkbdata is generally not maintained, I am closing this one. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.