Projects like libxklavier and the GNOME keyboard configuration control panel have started using the libxkbfile API to determine the Xserver keyboard configuration. There are two major problems with this use of libxkbfile: 1) It requires the software to know where the X server in use has installed its XKB configuration files. If the user installs an alternate Xserver for whatever reason, the software may use incorrect configuration files or be unable to find XKB data files at all. 2) It requires local filesystem access to the configuration files of the Xserver so it won't work with remote displays. An enhanced or replacement API for libxkbfile should be developed to solve these issues.
See also http://bugzilla.gnome.org/show_bug.cgi?id=152105
i'll sort it
see also http://people.freedesktop.org/~daniels/talks/fosdem-xkb.pdf
<insert comment here>
(In reply to comment #3) > see also http://people.freedesktop.org/~daniels/talks/fosdem-xkb.pdf Daniel, this is really excellent presentation, I'd say - and it makes perfect sense to me. I really regret I could not attend it. Anyway, I am going to promote it as widely as I can.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
libxkbfile also mixes in other XKB API's that really should have been in libX11 with the rest of them, like XKBBell - most programs that link with libxkbfile don't actually read XKB files. (Though fewer today since we didn't get this converted well from Imake to automake for many of the Xorg apps.)
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libxkbfile/issues/1.
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.