- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 17:51:52 +0000
- To: public-css-archive@w3.org
(responding to the IRC log discussion in the comment above) Note that I18N spent a long time creating a document about string matching [Charmod-Norm](https://www.w3.org/TR/charmod-norm). When specifying string matching or when considering what to apply, consider referencing the best practices found there. In particular, I18N recommends ***against*** performing Unicode normalization for most matching regimes. I think our previous half-hearted recommendation to look at NFC for ruby base matching came out of a TPAC discussion in which NFKC was being considered. But upon reflection, if the base and ruby text were not encoded the same except under NFC, treating them as different would be unsurprising (and represents a pretty rare corner case in any event--the only case that springs to mind might be the handling of _dakuten_ marks in Japanese, which are sometimes combining, but even then the difference might be intentional??) -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5995#issuecomment-1332531471 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 17:51:54 UTC