- From: Henry Chan via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jun 2020 03:08:32 +0000
- To: public-css-archive@w3.org
The fonts based on the Tenghuaxie version submitted for ISO10646 standardization is 10MB in total. Only considering the Small Seal in Shuowenjiezi and its different versions, in [WG2 N4716](http://www.unicode.org/wg2/docs/n4716-VariationSelectorShuowenSmallSeal.pdf) page 6 there are five versions. If you look at [WG2 N5117](https://unicode.org/wg2/docs/n5117_ShuowenSealEncodingReport.pdf) page 8, there are even more versions. Not to mention actual Small Seal carvings are different from those illustrated in Shuowenjiezi in this article "目前坊间的小篆字体有什么区别？" (What's the difference between the different released small seal fonts" https://www.zhihu.com/question/41780292. There is still no consensus on how these will be handled in Unicode, and researchers mainly rely on PUA or putting the glyphs on top of their corresponding CJK Unified Ideographs. > Regarding the specific problem you mention though, I think, in a sense, thats the easier problem, where there is an expectation that sites can be updated. @tabatkins had a great suggestion for a way that sites could explicitly requests fonts off disk with user involvement, and I think would cover the use case you describe. That sounds great. For the case of legacy sites where content can't be updated, besides having a global setting, it might be easier for users to install a certain WebExtension which dynamically injects the necessary JavaScript to request access to fonts for required sites. -- GitHub Notification of comment by hfhchan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4497#issuecomment-651498001 using your GitHub account
Received on Tuesday, 30 June 2020 03:08:34 UTC