- From: Michael Scott Asato Cuthbert via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 May 2024 12:19:12 +0000
- To: public-css-archive@w3.org
If `<urange>` does disappear I hope that the `unicode-range` value can be specified more completely than just `<string>` for the aid of parsers. The ability to specify more than one (comma-separated) unicode range is at present scarcely documented, but is crucial for users of fonts whose ranges have been broken up due to historical circumstances in the unicode spec. The musical symbols ranges, for instance, is divided into at least two (three or more depending on completeness) ranges, and some fonts (including the W3C Standard Music Font Layout, SMuFL which defines both Unicode standard and Private Use definitions) depend on implementors being able to subset non-connected ranges to create composite-font rendering experiences. -- GitHub Notification of comment by mscuthbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8835#issuecomment-2092905529 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 May 2024 12:19:12 UTC