- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Dec 2019 18:01:47 +0000
- To: public-css-archive@w3.org
Adding script names or language names is a recurring request, and we do need to address it at some point. For example, this is both cumbersome and fragile against future additions: ``` @font-face { font-family: 'Headings'; src: url(fonts/Japanese.woff); unicode-range: U+A5, U+4E00-9FFF, U+30??, U+FF00-FF9F; /* yen, kanji, hiragana, katakana */ } ``` I agree with @Crissov that using an existing list, provided it is well maintained, well documented and readily available, is much better than getting into the business of script or language registries. It isn't clear to me that [ISO 15924:2004](https://www.iso.org/standard/29546.html) defines which characters are included in each script. I wasn't keen to spend the CHF 68 to find out. Anyone know? Or is that all contained in the registry? [Unicode® Standard Annex #24 Unicode Script Property](https://www.unicode.org/reports/tr24/) is online, and freely available, and appears to be a superset of ISO 15924. I'm happy that the [registry is online](https://unicode.org/iso15924/) and that Unicode is the registration authority. That at least means that ISO and Unicode are striving to be in alignment here (with a few exceptions, like Fractur and Gaelige being distinct in ISO 15924 and unified in Unicode UAX 24. I plan to reach out to the maintainers of the registry to confirm the exact status. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4573#issuecomment-563358024 using your GitHub account
Received on Monday, 9 December 2019 18:01:51 UTC