After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773919 - Use xkbcommon-compose instead of custom compose table mechanism
Use xkbcommon-compose instead of custom compose table mechanism
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Input Methods
3.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2016-11-03 21:50 UTC by Thibaut Girka
Modified: 2018-05-02 17:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thibaut Girka 2016-11-03 21:50:28 UTC 
Parsing and handling X Compose tables should be implemented using xkbcommon-compose instead of the custom table mechanism, which does not honor the XCOMPOSEFILE and XCOMPOSECACHE variables nor the “include” instruction of XCompose files, and may have other divergences with the XCompose spec.
Comment 1 Matthias Clasen 2016-11-04 15:23:38 UTC 
How well will that work on platforms other than linux ?

Anyway, patches would be welcome
Comment 2 Thibaut Girka 2016-11-04 15:44:27 UTC 
This is a good question.
I think it should at least work with any platform using X11, Wayland or Mir, and xkbcommon is actually already used in the last two backends (but not for the compose key functionality that xkbcommon also provides).
I am not sure how it would work on Windows.
Comment 3 Matthias Clasen 2018-01-18 18:24:57 UTC 
Patches still welcome
Comment 4 GNOME Infrastructure Team 2018-05-02 17:42:34 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME'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.gnome.org/GNOME/gtk/issues/696.