- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Dec 2021 10:34:58 +0000
- To: public-css-archive@w3.org
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? @litherum do you have any data on how often you encounter the legacy encondings compared to Unicode ones? What I find unfortunate is that fonts also show a '¥' for '\' U+005C when the text encoding is Unicode - which is not helping to phase out this font-based workaround longer term. As a proposal, would it make sense to add two stylistic sets to the listed fonts for two modes, i.e. 1) one where they show U+005C as yen sign and 2) one where they show U+005C as backslash? Then perhaps the "dont't convert" stylistic set (2) could be activated if the text encoding is Unicode-based? CC @peterconstable -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6848#issuecomment-983506490 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 10:35:00 UTC