Live data from Hacker News

Color Emoji in Windows 8.1 – The Future of Color Fonts?

opentype.info

51–60 of 74 posts

Re: Color Emoji in Windows 8.1 – The Future of Color Fonts?

#51

I can't read this article without allowing Javascript.

That is true for about 50% of the links posted here these days. I usually just close the tab and read the comments on HN.

Note to site designers: something is terribly wrong if JS is needed to render the main textual content of your site.

Re: Color Emoji in Windows 8.1 – The Future of Color Fonts?

#53
post #51

I can't read this article without allowing Javascript.

That is true for about 50% of the links posted here these days. I usually just close the tab and read the comments on HN. Note to site designers: something is terribly wrong if JS is needed to render the main textual content of your site.

Or just get with the program and allow JS. It's not going away, as flawed a language as it is.

Web browsers are an execution environment, no longer just document viewers.

Re: Color Emoji in Windows 8.1 – The Future of Color Fonts?

#54
post #40

Earlier quoted context omitted.

There is a separate emoji panel, but in my experience you tend to remember the name of the emoji used the most, and in 10-key mode it's pretty fast to type a 2 or 3 kana word. About the android phones, I was a bit surprised by the low quality of Japanese support. But I didn't try the ATOK keyboard nor the input available on Sony phones for instance, only the Google IME. To Apple's credit, they've been doing IME on th…

The Japanese android vendor keyboards do seem to be generally much more polished than google's effort, although the latter is ok for basic Japanese input. The main issue with conversion-based emoji seems to be discoverability.... Besides those reflecting basic concepts, there are tons of odd or intricate emoji that you'd never even imagine existed unless you saw them first; even once you know they exist, figuring out…

About discoverability, when you start being a heavy user, the next step is to have custom entries in the user dictionary. It's almost mandatory for 2chan style smileys[0] with 7 or 8 characters in a row, and it also helps for obscure characters, emoji or not (there was a time "girl moji"[1] was a thing, with every letter splitted into 2 or 3 parts. I can't imagine that thing working without having all the letters in a user dictionary).

[0] http://matsucon.net/material/dic/kao01.html [1] http://plaza.rakuten.co.jp/love2kaomoji/5007/

Re: Color Emoji in Windows 8.1 – The Future of Color Fonts?

#55
post #51

Earlier quoted context omitted.

That is true for about 50% of the links posted here these days. I usually just close the tab and read the comments on HN. Note to site designers: something is terribly wrong if JS is needed to render the main textual content of your site.

Or just get with the program and allow JS. It's not going away, as flawed a language as it is. Web browsers are an execution environment, no longer just document viewers.

What about Braille readers and stuff like that? How well do they support javascript?

Re: Color Emoji in Windows 8.1 – The Future of Color Fonts?

#58
post #55

Earlier quoted context omitted.

Or just get with the program and allow JS. It's not going away, as flawed a language as it is. Web browsers are an execution environment, no longer just document viewers.

What about Braille readers and stuff like that? How well do they support javascript?

Reportedly, accessible browsers do support JavaScript well enough. Modern ones are usually based on WebKit. They have to contend with the real world of websites (already) using JS to display content.

Re: Color Emoji in Windows 8.1 – The Future of Color Fonts?

#60
post #51

Earlier quoted context omitted.

That is true for about 50% of the links posted here these days. I usually just close the tab and read the comments on HN. Note to site designers: something is terribly wrong if JS is needed to render the main textual content of your site.

Or just get with the program and allow JS. It's not going away, as flawed a language as it is. Web browsers are an execution environment, no longer just document viewers.

But why should viewing a document require javascript execution?
Post reply on HN