- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Sep 2024 11:02:10 +0000
- To: public-css-archive@w3.org
> This looks like a bit of a hack, since `unicode-range` does not currently have a syntax that excludes certain Unicode code points, which should theoretically be used here: `unicode-range: exclude(latin)`. > > Otherwise, it's hard for the author to define what is Chinese, so it's best to have an exclusion syntax where the rest of the characters are looked up from the defined font. Agreed; more flexible and expressive unicode-range options would be nice for many reasons. > Also, does this affect performance? In principle it probably improves performance compared to doing the `font-family: Arial, CJK-font, sans-serif;` pattern for text that is primarily CJK, because it avoids making the browser first check Arial for each CJK character (only to find that it is not supported there). In practice the difference may well be pretty insignificant. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10928#issuecomment-2370944192 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 September 2024 11:02:11 UTC