- From: Patrick Dark via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Feb 2021 04:19:21 +0000
- To: public-css-archive@w3.org
I expanded upon the cited email at https://github.com/w3c/csswg-drafts/issues/5927#issuecomment-779562023. Even though it wouldn't solve all of the cited issues, I think Unicode normalization is probably a good idea. It would address the fullwidth versus normal width punctuation cases between CJK and Latin languages where I would expect a match (and autohiding). I also would expect Hangul characters built from component characters (Hangul Jamo) to match the precomposed versions, though I'm not sure where that would occur in practice. It would also allow matching in a weird case I ran into where I deliberately used a combining diacritic plus base letter variant of a character instead of the precomposed diacritic-plus-letter version because the latter was missing in a designer font I was using, so the former looked better. In this case, while I was using ruby, I didn't have to match anything, but would nevertheless expect a match in a comparison to the precomposed character. -- GitHub Notification of comment by patrickdark Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5995#issuecomment-779570631 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 February 2021 04:19:23 UTC