Bug 19378 - Improved support for input order on diacritics via compose key.
Summary: Improved support for input order on diacritics via compose key.
Status: RESOLVED DUPLICATE of bug 3138
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xlib (data) (show other bugs)
Version: 7.4 (2008.09)
Hardware: All All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-03 08:32 UTC by Pander
Modified: 2009-03-12 19:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Pander 2009-01-03 08:32:48 UTC
Regarding libx11-data 2:1.1.5-2ubuntu1.1

When activating the compose key, e.g. to the windows keys, the functionality
regarding the input order is not optimal.

The input order for creating characters with diacritics like é (small e with acute accent) is now compose->'->e, but compose->e->' should result in the same, but at the moment is resulting in nothing.

The latter import order is like in our natural language. People talk and think about an 'e' with a certain accent, it should be possible to enter it like that and it is much brain friendlier.

For adding diacritics (and preferably for all compositions) I would like to
request that the compose key functions regardless the input order or at least
also support the other way around for the diacritics in combination with all vowels.

Improving compose key like this allows for higher user satisfaction when
entering characters with diacritics in an easier and more brain friendly way.
Comment 1 Pander 2009-01-03 18:49:31 UTC
See also the same bug for GNOME/ GTK with its own compose functionality: http://bugzilla.gnome.org/show_bug.cgi?id=565912 Both are separate bugs but regarding the same functional requirement.
Comment 2 Alan Coopersmith 2009-03-12 19:53:03 UTC

*** This bug has been marked as a duplicate of bug 3138 ***


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.