On Wed, Jan 18, 2017 at 9:38 AM, Jonathan Kew <jfkth...@gmail.com> wrote: > Note that the current CSS Fonts 3 spec explicitly says that UAs are required > to recognize localized font names: > > "Some font formats allow fonts to carry multiple localizations of the family > name. User agents must recognize and correctly match all of these names > independent of the underlying platform localization, system API used or > document encoding..."[1] > > (The Hebrew name of Raanana is even included in the examples shown there!) > > As you've noted, Chrome does not actually support this, so there is not full > interoperability in this area; but if we decide to remove this support (and > don't implement any of the possible workarounds) then I think we need to > bring it up in the CSS WG and see if there is agreement on explicitly > changing it in the spec. (I'm not sure how readily Apple and Microsoft will > buy into that, as I believe there is historically some usage of localized > font names on both macOS and Windows, though clearly Chrome hasn't > considered it essential.) > > Anyway, just wanted to point out that this is a spec issue, not something we > should decide in isolation. > > JK > > [1] https://drafts.csswg.org/css-fonts-3/#font-family-prop
Is it currently the case that all major APIs (i.e., CoreFoundation, GDK, Direct2D, FreeType, etc.) read all localisations of family name? Like, will Direct2D read MacHebrew encoded names? If not, then the only way to be compliant with what Fonts 3 says is for the browser to support every possible character encoding in OpenType (IIRC that's a closed set?) and convert it to something the system API can read? I believe it's not, and I doubt anyone is going to implement that, hence I'd guess the spec needs to change anyway. /g _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
