- From: Christoph Päper via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Mar 2018 11:45:14 +0000
- To: public-css-archive@w3.org
I’m afraid we have two closely related but different issues at hand. 1. Ignoring all VSs. 2. Specifying fallback in case the VS sequence has no glyph in the current font but the base character does. The first issue, which I proposed independently, is in scope of [css-text], the second sounds more like [css-fonts] was the right place indeed. Unicode does not concern itself with font selection much, so while it clearly mandates that the default glyph of the base character should be shown instead of no glyph (other than `.notdef`), it does not say whether choosing an alternative font that does have a glyph for the SVS would be preferred over that. Unless I missed something or course. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1710#issuecomment-371113364 using your GitHub account
Received on Wednesday, 7 March 2018 11:45:19 UTC