- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Dec 2021 20:15:49 +0000
- To: public-css-archive@w3.org
@drott > Do I understand correctly, that WebKit performs the character replacement as well if the text encoding is a Unicode encoding (say UTF-8, UTF-16) and only the font name is one of the MS Japanese ones? Correct. We do the replacement if the encoding is one of the ones listed above, or if the requested font name is one of the above. If content is UTF-8 and has `font-family: MS PGothic`, we'll do the replacement. > do you have any data on how often you encounter the legacy encodings compared to Unicode ones? I don't. (Are you considering Shift JIS 'legacy'? It's still fairly popular - [Wikipedia says](https://en.wikipedia.org/wiki/Shift_JIS) "Shift JIS is the second-most popular character encoding for Japanese websites, used by 5.6% of sites in the .jp domain.") > would it make sense to add two stylistic sets to the listed fonts It looks like Meiryo maps U+005C to yen but has a seemingly-unused lookup to substitute it to backslash; MS Mincho maps U+005C to yen but has no such lookup. @PeterConstable What do you think about @drott's [proposal above](https://github.com/w3c/csswg-drafts/issues/6848#issuecomment-983506490)? -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6848#issuecomment-984019775 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 December 2021 20:15:51 UTC