- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Oct 2022 16:37:10 +0000
- To: public-css-archive@w3.org
> For this, I'd propose allowing <string> as well, and treating it as specifying the set that is derived from the union of all codepoints in the string. E.g. this would be valid: > > unicode-range: "&"; It may also be useful (i haven't thought it through completely) to allow ranges separated by hyphens, like: `unicode-range: "&¡-§©"` which would include the characters &¡¢£¤¥¦§©. You'd need a way of escaping the - character though. (Two other cautions about situations where it may be better to stick with code point numbers: [1] Using characters instead of code point values may cause some difficulty when specifying RTL character sets. For example in unicode-range: "ذ-خ", "ى", "a-z", "ب-ت"; the underlying order is not what you see (although it could be worse). [2] You'll probably still want to use code point values for combining characters and invisible characters, and especially for formatting characters such as RLI/LRI etc which will again make the declaration look odd. ) -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7921#issuecomment-1293792169 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 October 2022 16:37:12 UTC