Re: [whatwg] Unicode -> ASCII copy/paste fallback

On Fri, Feb 13, 2015 at 1:08 PM, Nils Dagsson Moskopp
<nils@dieweltistgarnichtso.net> wrote:
> David Sheets <kosmo.zb@gmail.com> writes:
>
>> On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
>> <james.m.greene@gmail.com> wrote:
>>> In this case, you can use Unicode escape values by preceding them with a
>>> slash:
>>>
>>>   .rarr:after { content: "\2192"; }
>>>
>>>
>>> This is specified in the CSS 2.1 spec:
>>> http://www.w3.org/TR/CSS2/syndata.html#characters
>>>
>>> Personally, I probably would've just started on StackOverflow with this
>>> question (e.g. [1]) but no harm done.
>>
>> Hi James!
>>
>> Sorry, I wasn't clear. The issue is not with putting Unicode values
>> into CSS. The issue is that I would like unicode values to be copied
>> and pasted as a specific ASCII fallback value.
>>
>> That is, I would like the equivalent of "a &rarr; b" to appear on a
>> page but, upon copying, "a -> b" to show up in the clipboard.
>>
>> I have a solution that works in Firefox 36 (described in original
>> mail). Chrome 40 does not behave similarly.
>>
>> I can see some arguments for Chrome's behavior along security lines. I
>> certainly can understand the utility of Firefox's behavior because I
>> am writing a documentation generation tool for a programming language
>> with right arrows represented as -> but would like to render them as
>> →.
>
> I would suggest to use OpenType ligatures for that. You could reasonably
> create a ligature font that renders any occurence of “->” as “→”.

This is a really brilliant solution that satisfies my use case
perfectly. I created the following (horrible) font that works as
expected.

<data:application/font-woff;base64,d09GRk9UVE8AAAXQAA0AAAAACAwAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAABDRkYgAAABMAAAAY4AAAGdFwHC50ZGVE0AAALAAAAAHAAAABxuRRqXR0RFRgAAAtwAAAAqAAAANABJADhHUE9TAAADCAAAACAAAAAgRHZMdUdTVUIAAAMoAAAAQAAAAFCxBbQIT1MvMgAAA2gAAABHAAAAYFYhYsBjbWFwAAADsAAAAEMAAAFKAmIC1WhlYWQAAAP0AAAAMAAAADYFFMPmaGhlYQAABCQAAAAdAAAAJAZsBDtobXR4AAAERAAAABQAAAAUEegCzm1heHAAAARYAAAABgAAAAYABVAAbmFtZQAABGAAAAFZAAACi0q47Qlwb3N0AAAFvAAAABMAAAAg/4MAM3icRY9BSxtRFIXvSzINhuGlCZlGwjSORGgL6cRKcSFmY0gQYtMoVupKDHnJhNYoydMacOdCcewu0EV2pf8gUOlm6EY63ZdCV8WV/gG9z7xAjF2kZ3XOtzjwEfD5gBASeFPnNf6elV8A8QCBJREE8ZiIuEdMeEXUF7/wfBmo3vjy54HqiwdgbG8tZdujovqRfu+N3ZqKDn+DOsBDHa5COoR1YodBuX8MQhTWoQTvrNaOxeob1Qbb5KxR2Nxir5g5k/k3y0apZZSbFmO8mUwmjQ81bhm57TrPbTeqzJgxp42nFuc7c6lUZUgr99RsVsw6489GBv9VhqEwQY7IMSiETM2+3u30Q7Yjig5xHHQdr/NImOJr33zg9A81UUS3X/RT/IYJgpNiUZOJ2wNMDMm56GqYk0wW5fJlCn/hmezgb4ViFylBKp5rtqRi/GQh7WYxg5nTH3IVm9kCKjKs0Bt0MUbwpShoH2VMuHb6yc8szuOK/Ue+xf18/lpGFNprR3ohzVYDmAgg/dRW1Ttgr6BKAAAAAAABAAAAAMw9os8AAAAA0QO3ygAAAADRA7/9eJwlibENACAMwxzamSsY+f8+XKHI9hACbDlcvSiiY8u2i8wD+TwTFwCCAAAAAQAAAAoAHAAeAAFERkxUAAgABAAAAAD//wAAAAAAAHicY2BkYGDgYpBj0GFgdHHzCWHgYGABijD8/88AkmHMyUxPBIoxQHhAORYwzQHEQlCahYGZgQkIGUEQACkoBXB4nGNgYWFg/MLAysDANJPpDAMDQz+EZnzNYMzICRRlYGNmgAFGBiQQkOaawnCAQZfBjtn4vzFDDNOs/6dR1CgAIRMAc0gMkAB4nGNgYGBmgGAZBkYGEHAB8hjBfBYGDSDNBqQZGZgYdBns/v8H8sH0/yv/j0DVAwEjGwOCQwzAUMxEiu5BCQAKpAk1AHicY2BkYGAA4hCza8vj+W2+MnCzMIDAReYDvHC6isGUuZRpFpDLwcAEEgUABpUIx3icY2BkYGCaxWDKEMPCAALMpQyMDKiAFQAsSwGxAAAAAgAAAAQAAI0EAAEnBAAAegPoAKAAAFAAAAUAAHichZDNSsNAFIXP9A8KItInmI1QIU0nKd1kaaGI4NLuWzJpAjUpyZTSrYgrn8VXcO3atWufwJ0LT6ZjQQSbYe797uHOmTsBcIpnCOy/Szw6Fuji3XEDHXw6buJcXDluoSvuHbdxJn58OtTf2ClaXVYP9lTNAj28Om7gBB+Om7jGl+MWeiJ33IYUT4471F8wQQmNOQxjDIkFdowxKqRUNPUKnl0SW2SsU9IUBXJynUss2ScRwodi7rPDcK0RYciVuN7k0OvTM2HMrf8FMCn13OhYLnYyrlKtTeV5ntxmJpXTIjfTolxqGfpK9lNj1tFwmFBNatWvEj/Xhh639pJ6wJV9SkApN5lZ6Zh4Y7UMG9yx0HG2Yf7vFRH3X8u9HmCEATvrrViNafVrzEgeriYHo0E4CFUwPjbkjFrJf5PZuSS9a3ff5nomzHRZZUUulQp8pZQ8YvgNzG5wnAAAAHicY2BmAIP/DQzGDFgAACgUAbYA>

The browser inconsistency in the original case still stands, though.
Is there a spec covering copy and paste?

David

> --
> Nils Dagsson Moskopp // erlehmann
> <http://dieweltistgarnichtso.net>

Received on Friday, 13 February 2015 15:07:46 UTC