Bug 3775 - [BROKEN_BUG] Missing "HORIZONTAL ELLIPSIS" from Compose maps
Summary: [BROKEN_BUG] Missing "HORIZONTAL ELLIPSIS" from Compose maps
Status: CLOSED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xlib (show other bugs)
Version: unspecified
Hardware: All All
: high minor
Assignee: Jim Gettys
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-14 23:49 UTC by Daniel Stone
Modified: 2011-10-15 17:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description FreeDesktop Bugzilla Database Corruption Fix User 2005-07-14 23:49:44 UTC
In the lib/X11/locale tree, there are no Multi_key definitions for HORIZONTAL
ELLIPSIS U2026.

Now I know there are some keyboards that ship with an ellipsis key, but I don't
have one.  So it would be good to have a Multi_key combination that does this. 
I suggest that <Multi_key> <comma> <period> be used, as this is easy to type on
most keyboards, requiring four keystrokes at most.
Comment 1 Simos Xenitellis 2007-06-22 12:32:52 UTC
Horizontal ellipsis is U+2026 (…).
The majority of the members of the punctuation Unicode group is missing from the Compose file. It would make sense to add the whole lot in a uniform way, instead of creating single sequences.

In any case, here is the missing compose sequence,

<Multi_key> <period> <period> <period>     : "…" U2026 # HORIZONTAL ELLIPSIS
Comment 2 Benjamin Close 2008-01-11 02:36:52 UTC
Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler
Comment 3 Jeremy Huddleston Sequoia 2011-09-24 20:58:35 UTC
Looks good to me in the current libX11

~/src/freedesktop/src/libX11/nls/en_US.UTF-8 (master) $ grep … *
Compose:<Multi_key> <period> <period>    	: "…"   ellipsis # HORIZONTAL ELLIPSIS
Compose.pre:<Multi_key> <period> <period>    	: "…"   ellipsis # HORIZONTAL ELLIPSIS


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.