- From: Masataka Yakura via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Aug 2022 02:36:46 +0000
- To: public-css-archive@w3.org
Although I'm not strongly against about it, I don't think it's worth the change to the specs and implementations. I don't know how things are going on in #3135 , but if the `ic` requires implementations to download the font, then 永 (U+6C38) has higher chance to cause extra font download compared to 水 (U+6C34): * In [Noto Sans Japanese](https://fonts.googleapis.com/css2?family=Noto+Sans+JP), 水 (U+6C34) is placed in the 5th most used characters bucket, whereas 永 (U+6C38) is in the 22nd * In [Noto Sans Traditional Chinese](https://fonts.googleapis.com/css2?family=Noto+Sans+TC), 水 is in the 2nd bucket, and 永 is in the 5th * In [Noto Sans Simplified Chinese](https://fonts.googleapis.com/css2?family=Noto+Sans+SC), 水 is in the 3rd bucket, and 永 is in the 6th * In [Noto Sans Hong Kong](https://fonts.googleapis.com/css2?family=Noto+Sans+TC), 水 is in the 2nd bucket, and 永 is in the 5th * In [Noto Sans Korean](https://fonts.googleapis.com/css2?family=Noto+Sans+KR), 水 is in the 16th bucket, and 永 is in the 39th -- GitHub Notification of comment by myakura Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7577#issuecomment-1210082393 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 August 2022 02:36:47 UTC