- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Oct 2018 17:21:37 +0000
- To: public-css-archive@w3.org
IIRC, Firefox currently builds its own psname and fullname indexes (of English names only, or first available locale if no English present) for each font face, on all platforms *except* macOS, where it relies on CGFontCreateWithFontName, which helpfully matches on both psname and fullname.
(Unfortunately, https://developer.apple.com/documentation/coregraphics/1396330-cgfontcreatewithfontname doesn't specify how localized names are handled. A brief test seems to suggest that it does *not* match all locales.)
I guess we could collect all localized names on the platforms where we build our own indexes, rather than just the English (or first) name, but I'm not particularly keen; ISTM that it adds very little value.
I think the potential "inconsistency" the current spec text is trying to avoid is that the collection of localized names in a font may well vary over time/versions, and/or between locales where the font is made available, while still being "the same font" in the sense that src:local would be expected to match it. (Noting that src:local is appropriate when a particular typeface is wanted, but the exact version of the resource is not important.) Virtually all font resources include English names, so these can be matched reliably, but if src:local is allowed to match all localized names, this introduces the risk that an author may write `src:local("Arial Fett")`, but on a user's system the equivalent font provides only "Arial Gras" as a localized alternative and so it is missed.
Declaring that src:local consistently matches against English names (and only those) is intended to minimize such issues.
--
GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3177#issuecomment-433999894 using your GitHub account
Received on Monday, 29 October 2018 17:21:39 UTC