- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 08:46:42 +0000
- To: public-css-archive@w3.org
> But in practice "the default user interface font" is not a single font; as the note in Example 6 suggests, it is really a collection of fonts -- otherwise not all languages would be able to be displayed in the UI. Right, most modern OS have the mechanism to link or fallback multiple physical fonts. We agree on this point, right? As you know, the "font set" (or "font fallback list" or "font link set") usually vary by the platform UI langauge. IIRC, macOS stores a list of fonts in a plist, that can have if-branch by the language, if my knowledge isn't outdated. For this issue, I think the question is whether the "font set" emulation in the browser should be the "font set" of the platform language, or of the content language. I think the original motivation was to expose the "font set" mechanism, in order for web apps to have the same look-and-feel with other native apps. From that perspective, I assumed that it's platform language, because all other apps are in the platform language. If we want to change that, or if it was my misunderstanding, I'm fine, but as far as I know, it's technically not possible on Windows. If we were changing this, I wish us to make sure it's implementable on all platforms. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9518#issuecomment-1778799031 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 October 2023 08:46:44 UTC