- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Oct 2018 13:06:12 +0000
- To: public-css-archive@w3.org
- **Windows**: As mentioned in the [original issue report](https://github.com/w3c/csswg-drafts/issues/3177#issue-364457351) Microsoft's DirectWrite API for font matching allows specifiying a locale, or when leaving it out, matches all locales, details here [IDWriteFontSet::GetMatchingFonts](https://docs.microsoft.com/en-us/windows/desktop/api/dwrite_3/ns-dwrite_3-dwrite_font_property), so for the implementation on Windows 10 I do not see any restrictions. For older Windows versions, [IDWriteFont::GetInformationalStrings](https://docs.microsoft.com/en-us/windows/desktop/api/dwrite/nf-dwrite-idwritefont-getinformationalstrings) returns a IDWriteLocalizedStrings pointer which allows access to all localized forms of the full font name and postscript names, which allows building a lookup structure to match against all localized name variants. - **Linux / ChromeOS**: Fontconfig PS name and full font name matching is also not restricted by locale. - **Android**: For Chrome on Android, we implemented our own indexing mechanism which can also match all locales, since it reads information directly from the font files. Perhaps @jfkthame can comment for FF. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3177#issuecomment-433902460 using your GitHub account
Received on Monday, 29 October 2018 13:06:13 UTC