- From: DeeDeeG via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Apr 2017 07:48:51 +0000
- To: public-css-archive@w3.org
(I'm new to this discussion, so forgive me if I'm off-base or if this makes no sense to the discussion) Unicode have been very loose about what Variation Selector 15 and Variation Selector 16 should mean. See this chart from Wikipedia: https://en.wikipedia.org/wiki/Emoji#Emoji_versus_text_presentation Unicode basically says, VS-15 *SUGGESTS* plain-text, or VS16 *SUGGESTS* colorful emoji, but let the user-agent decide. The User Agent (whatever app you're running) has the ultimate say. In that frame of mind... the 5-options proposal (with auto, text, emoji, emoji-override, text-overide) seems good, and follows in the spirit of Unicode's "flexibility, complexity and control" intentions. So I want to go with the 5 options, because it validates the work they've put in. But taking a step back, I don't see the point in being complex if the end result isn't actually better for it. Upon reconsidering, I want to go with the 3-option proposal (auto, text, emoji). The way I understand the 5-options proposal, the Unicode folks described "default", "text" and "emoji" as always being functionally equivalent: follow the VS hints, and also follow Emoji_Presentation default guidelines from here: http://unicode.org/emoji/charts/text-style.html Seems kind of redundant, so why not just do it this way?: - Default (obey VS hints and default presentation guidelines from Unicode), - Text (don't obey VS hints or default presentation guidelines from Unicode, make characters "text" if at all possible), - Emoji (don't obey VS hints or default presentation guidelines from Unicode, make characters "emoji" if at all possible) -- GitHub Notification of comment by DeeDeeG Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1144#issuecomment-294278435 using your GitHub account
Received on Saturday, 15 April 2017 07:48:58 UTC