- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 May 2025 15:51:34 +0000
- To: public-css-archive@w3.org
Hmm, we need to be careful here to pay attention to exactly which names we're talking about. CSS Fonts 4 says that localized *family names* must be matched, but it also says (in [4.3.3.1. Local font fallback](https://drafts.csswg.org/css-fonts-4/#local-font-fallback)) that localized *full font names* must **not** be matched; only the en-US full name (or first localization, if en-US is not present) is to be matched by `src: local(...)`. And when used directly in `font-family`, matching *any* full name would be an error: *full name* ≠ *family name*. (See also [2.1.4. Relationship Between Faces and Families](https://drafts.csswg.org/css-fonts-4/#font-families).) In the case of [font-family-name-015.xht](https://github.com/web-platform-tests/wpt/blob/6869c15e7e/css/css-fonts/font-family-name-015.xht), the name it uses "ＣＳＳテスト フォント名 Bold" looks like it's a localized *full* (not *family*) name, and as such the test is correct to assert that it should not match (either for `font-family`, as in the test, or if it were to be used in a `@font-face` rule's `src:local(...)`). I think the primary reason for the failures currently seen on wpt.fyi is that the CSS test fonts aren't installed on the machines running the tests. (ISTR seeing some recent activity that looked like someone is in the process of making them available, so this situation may improve shortly.) Once the test fonts are actually installed, we can review the validity of whatever test failures remain. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12207#issuecomment-2887104728 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 May 2025 15:51:35 UTC