David Sheets writes:
> On Sun, Feb 15, 2015 at 3:16 AM, Glenn Maynard wrote:
>> On Sat, Feb 14, 2015 at 12:34 PM, David Sheets wrote:
>>>
>>> I am writing a documentation generation tool for a programming
>>> language with right arrows
On Sun, Feb 15, 2015 at 3:16 AM, Glenn Maynard gl...@zewt.org wrote:
On Sat, Feb 14, 2015 at 12:34 PM, David Sheets kosmo...@gmail.com wrote:
I am writing a documentation generation tool for a programming
language with right arrows represented as - but would like to render
them as →.
On Sun, Feb 15, 2015 at 4:40 AM, David Sheets kosmo...@gmail.com wrote:
If you're reading documentation which includes types, it's nice to see
implication arrows but copy valid syntax.
This is rather vague, but it sounds along the lines of using → for
pointer dereferencing in a C++ document,
On Fri, Feb 13, 2015 at 11:11 PM, Glenn Maynard gl...@zewt.org wrote:
On Fri, Feb 13, 2015 at 9:02 AM, Glenn Maynard gl...@zewt.org wrote:
Copying ASCII isn't desirable. It should copy the Unicode string a → b.
After all, that's what gets copied if you had done spana → b/span in
the first
On Fri, Feb 13, 2015 at 10:23 PM, Ashley Gullen ash...@scirra.com wrote:
Why is it desirable to copy ASCII versions of unicode text? Doesn't most
software now support unicode so the user can copy and paste what they see,
rather than some ASCII-art equivalent?
I am writing a documentation
On Sat, Feb 14, 2015 at 12:34 PM, David Sheets kosmo...@gmail.com wrote:
I am writing a documentation generation tool for a programming
language with right arrows represented as - but would like to render
them as →. Programmers are used to writing in ASCII and reading
typeset mathematics. If
David Sheets kosmo...@gmail.com writes:
On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
james.m.gre...@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:
On Fri, Feb 13, 2015 at 5:45 AM, David Sheets kosmo...@gmail.com wrote:
Hello,
I have a page with
a span class=rarrspan-gt;/span/span b
and style
.rarr span { overflow: hidden; height: 0; width: 0; display: inline-block;
}
.rarr::after { content: →; }
(That's RIGHTWARDS ARROW x2192.)
David Sheets kosmo...@gmail.com writes:
On Fri, Feb 13, 2015 at 12:23 PM, Mathias Bynens mathi...@opera.com wrote:
On Fri, Feb 13, 2015 at 1:18 PM, James M. Greene
james.m.gre...@gmail.com wrote:
In this case, you can use Unicode escape values by preceding them with a
slash:
OP’s question
On Fri, Feb 13, 2015 at 1:08 PM, Nils Dagsson Moskopp
n...@dieweltistgarnichtso.net wrote:
David Sheets kosmo...@gmail.com writes:
On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
james.m.gre...@gmail.com wrote:
In this case, you can use Unicode escape values by preceding them with a
slash:
On Fri, Feb 13, 2015 at 3:02 PM, Glenn Maynard gl...@zewt.org wrote:
On Fri, Feb 13, 2015 at 5:45 AM, David Sheets kosmo...@gmail.com wrote:
Hello,
I have a page with
a span class=rarrspan-gt;/span/span b
and style
.rarr span { overflow: hidden; height: 0; width: 0; display:
On 2/13/15 10:15 AM, David Sheets wrote:
I suppose currently Chrome is preventing copying hidden content but
Firefox is not and neither picks up the CSS content.
Both prevent copying hidden content, but may not have identical
definitions of hidden.
Neither picks up CSS generated content,
Why is it desirable to copy ASCII versions of unicode text? Doesn't most
software now support unicode so the user can copy and paste what they see,
rather than some ASCII-art equivalent?
On 13 February 2015 at 15:45, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/13/15 10:15 AM, David Sheets wrote:
On Fri, Feb 13, 2015 at 9:02 AM, Glenn Maynard gl...@zewt.org wrote:
Copying ASCII isn't desirable. It should copy the Unicode string a →
b. After all, that's what gets copied if you had done spana →
b/span in the first place.
(Oh, I missed the obvious--the - from Firefox is coming from
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])
On Fri, Feb 13, 2015 at 1:18 PM, James M. Greene
james.m.gre...@gmail.com wrote:
In this case, you can use Unicode escape values by preceding them with a
slash:
OP’s question wasn’t about how to escape non-ASCII characters, but
rather about what the copy/paste behavior should be in browsers.
On Fri, Feb 13, 2015 at 12:18 PM, James M. Greene
james.m.gre...@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
On Fri, Feb 13, 2015 at 12:23 PM, Mathias Bynens mathi...@opera.com wrote:
On Fri, Feb 13, 2015 at 1:18 PM, James M. Greene
james.m.gre...@gmail.com wrote:
In this case, you can use Unicode escape values by preceding them with a
slash:
OP’s question wasn’t about how to escape non-ASCII
Sorry, David Mathias. Hasty 6:00am reply here before my brain and eyes
fully woke up!
Interesting question. Personally, I would expect and desire the
CSS-generated content to be copied.
Sincerely,
James M. Greene
On Feb 13, 2015 6:24 AM, David Sheets kosmo...@gmail.com wrote:
On Fri, Feb
To expand on my own comment:
Personally, I would expect and desire the CSS-generated content to be
copied.
...because THAT is what the user sees, per the browser rendering. I'm
surprised that neither Firefox nor Chrome exhibits that behavior.
Sincerely,
James M. Greene
On Feb 13, 2015 6:30
20 matches
Mail list logo