W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2017

Re: [csswg-drafts] [css-fonts] Consider specifying UA should not perform system fallback for Unicode PUA

From: Christoph Päper via GitHub <sysbot+gh@w3.org>
Date: Tue, 19 Dec 2017 13:04:12 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-352742981-1513688650-sysbot+gh@w3.org>
A common scenario where using system fonts for PUA codepoints as a fallback leads to undesired results is indeed an icon font (e.g. [Typicons at U+E000..F1FF](http://s-ings.com/typicons/)), being unavailable but using partially the same codes as the system emoji font does for pre-Unicode compatibility (e.g. Apple Color Emoji for SoftBank [ca. U+E000..E4FF](http://unicode.org/~scherer/emoji4unicode/snapshot/full.html)), although mostly icon fonts use U+F*xyz* and legacy emojis U+E*xyz* (or even U+FE*xyz*).

There are other fields that have coordinated PUA usage across fonts: constructed scripts (esp. [CSUR](http://www.evertype.com/standards/csur/)) and historic scripts (e.g. [MUFI](http://folk.uib.no/hnooh/mufi/)). I'm just pointing this out to make sure nobody thinks it would be okay to limit lookup of PUA characters to the first font in the stack.

GitHub Notification of comment by Crissov
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2110#issuecomment-352742981 using your GitHub account
Received on Tuesday, 19 December 2017 13:04:18 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:21 UTC