- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Feb 2019 16:20:42 +0000
- To: public-css-archive@w3.org
So there have, since the earliest days of fonts on the wen in like 1996-7, two schools of thought on selecting fonts. One is the 'DTP style' where for every piece of styled text, you select a specific face and you use the fully-qualified name there; it completely over-rides all aspects of any textual styling applied to any parent piece. So you would select, say, `18pt Helvetica Condensed Book Oblique`. This works fine with unstructured or lightly-structured (DTP, word-processor) text and was especially popular when there were significant operating system limitations (like when Windows allowed a maximum of four faces in a family). The other approach is structured: selecting a face selects a number of things (family, weight, style, size, etc) all of which may be individually overridden on a child element. This is needed when you have, say: ``` <p>Some text <b>some<i>more<span>text</span></i></p> ``` and the `p` is styled with Helvetica Book, the `b` inside that is Helvetica Bold, the `i` inside that is Helvetica Bold Oblique and the `span` changes the font family to Garamond, and you get Garamond Bold Italic. Even in the CSS1 days, when condensed and expanded being in the same family was more hope than reality, and even when the Latin and the Cyrillic versions of a face were clearly in separate font files (because fonts had a max of 256 glyphs) this was the model adopted by CSS. So the problem is not so much allowing `Noto Sans Blk` with a fully-specified font weight, as you have here; it is more when people override `Helvetica Light` with `Noto Sans Blk`, just changing the family name, and expect the weight etc to magically change along with it. The point about matching on localized names is a separate issue, which I thought was already open, but I'm not fining it right now. I'm going to post this comment now anyway, before I forget. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3691#issuecomment-468336054 using your GitHub account
Received on Thursday, 28 February 2019 16:20:43 UTC