W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2019

Re: [csswg-drafts] [css-fonts] Specify what generic font family maps to nastaliq (#4397)

From: c933103 via GitHub <sysbot+gh@w3.org>
Date: Mon, 16 Dec 2019 04:06:04 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-565896651-1576469163-sysbot+gh@w3.org>
Let me repeat my opinion here, I don't think it is a good idea to specify nastaliq or fraktur as new font family. They are specific ways to write their script with different regional preference on their usage, unlike regular font fanily which is supposed to be accessible to everyone who use the script. They have also been identified as different scripts in the ISO 15924 standard, and thus it is already possible to specify displaying content in these different writing variants through script subtag in language tagging, or user custom locale selection. Whether those platforms actually support them yet is another question, but support for similar variants have already been implemented on various platform, including the use of different fonts for same character with same Unicode code point on Japanese/Korean/Traditional Chinese/Simplified Chinese, or with Russian/Macedonian Italic Cyrillic glyph, or with Mathematics/Greek character beta. It is also possible, as have been done on some tools for Chinese/Korean/Japanese, to appoint different fonts based on different language/script combination, so that same string of character could display with different user-selected fonts under different language-script settings, displaying different writing style.
Another thing to consider is that, when there are enough font for e.g. Nastaliq on the market, undoubtedly fontmakers will also start making those fonts in different looks and the different among themselves will more closely resemble the difference between traditional font families in css. If nastaliq is to be specified and used as a font family then it would not be possible to specify those different font variants through font family unless additional font families are to be created for such different combinations.

-- 
GitHub Notification of comment by c933103
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4397#issuecomment-565896651 using your GitHub account
Received on Monday, 16 December 2019 04:06:13 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:27:05 UTC