- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Nov 2021 19:40:05 +0000
- To: public-css-archive@w3.org
@fantasai wrote > The spec should be defined so that any IANA-registered font subtype is a valid argument to format(). We shouldn't need to maintain this registry ourselves now that there is a standard one. On the one hand, as editor of RFC 8081 I agree that would be nice and that registry already exists. On the other hand, [4.4. Subtype Registrations](https://datatracker.ietf.org/doc/html/rfc8081#section-4.4) says: > For each subtype, an @font-face format identifier is listed. This is for use with the @font-face src descriptor, defined by the Cascading Style Sheets Level 3 (CSS3) Fonts specification [W3C.CR-css-fonts-3-20131003]. That specification is **normative**; the identifiers here are **informative**. so we have a bit of a catch-22 situation. But I think we can fix that by having Fonts 4 (which will supersede Fonts 3) normatively say that a) the IANA font subtypes registry is normative :) b) the `format identifier` is identical to the `font subtype` -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6328#issuecomment-964474981 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 November 2021 19:40:07 UTC