- From: DeeDeeG via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Aug 2018 01:19:06 +0000
- To: public-css-archive@w3.org
I hope it's okay to comment here again, even though this has been discussed and set as "resolved" and "closed." I would understand if it gets ignored or declined to be considered, for that reason. But anyways, I can articulate better why I thought this was a good idea: - There are content authors who currently do not specify a font family in their websites, or who only specify "serif" or "sans-serif". - For these authors, a color font toggle would offer meaningful control over colorful vs plain presentation style, without having to begin naming specific fonts. - There are "traditional outline" emoji fonts that cover much of the emoji unicode ranges, such as `Symbola`, and `Noto Emoji` (The Android emoji font from early KitKat). - These fonts considered, the range of emoji codepoints for which color/plain presentation is ambiguous is effectively "all of them." - Rather than try to chase an annual update of the Unicode spec, this would apply cleanly irrespective of what direction Unicode takes withemoji standards. - emoji standards at Unicode are complex, have a tendency toward inventing new parameters and ret-conning existing but outmoded conventions in favor of new ones. Being agnostic to these standards is a boon to implementation/maintenance complexity for vendors, and shields against unpredictability from the Unicode side of things. -- GitHub Notification of comment by DeeDeeG Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2304#issuecomment-409774254 using your GitHub account
Received on Thursday, 2 August 2018 01:19:08 UTC