Re: [GHC] #10006: Add baseline ellipsis as unicode alternative to «..»
GHC
ghc-devs at haskell.org
Mon Jan 19 20:32:23 UTC 2015
#10006: Add baseline ellipsis as unicode alternative to «..»
-------------------------------------+-------------------------------------
Reporter: zardoz | Owner:
Type: feature request | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.8.4
(Parser) | Keywords:
Resolution: | Architecture:
Operating System: Unknown/Multiple | Unknown/Multiple
Type of failure: None/Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Revisions:
-------------------------------------+-------------------------------------
Description changed by zardoz:
Old description:
> While the current unicode syntax is overall very pleasing to the eye,
> writing the ellipsis as two periods («..») sticks out quite noticably. I
> would welcome it if the horizontal ellipsis (U+2026, «…») would be
> allowed in places where «..» can be written.
>
> I noticed that there was an old discussion on the mailing list which
> indicated that originally there was a unicode replacement for «..»,
> namely the midline ellipsis, which wasn’t considered a good choice and
> was removed from the syntax. The regular ellipsis would have the
> advantage that it is one of the more common «fancy» characters and mapped
> by default in the X server compose definitions; as such it’s rather well-
> accepted and sees use even on IRC and in blogs. So user’s would
> potentially benefit from the regular ellipsis, much more so than the more
> exotic midline ellipsis.
New description:
While the current unicode syntax is overall very pleasing to the eye,
writing the ellipsis as two periods («..») sticks out quite noticably. I
would welcome it if the horizontal ellipsis (U+2026, «…») would be allowed
in places where «..» can be written.
I noticed that there was an old discussion on the mailing list which
indicated that originally there was a unicode replacement for «..», namely
the midline ellipsis, which wasn’t considered a good choice and was
removed from the syntax. The regular ellipsis would have the advantage
that it is one of the more common «fancy» characters and mapped by default
in the X server compose definitions; as such it’s rather well-accepted and
sees use even on IRC and in blogs. So users would potentially benefit from
the regular ellipsis, much more so than the more exotic midline ellipsis.
--
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10006#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list