- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Oct 2023 00:30:05 +0000
- To: public-css-archive@w3.org
> The "[fullwidth opening punctuation](https://drafts.csswg.org/css-text-4/#fullwidth-opening-punctuation)" includes quotation marks, so the test matches the spec without needing to including `Pf`. You're right, sorry, I had missed that part. That makes my first point irrelevant. > > Further, thoes tests makes it conditional on the language, collapsing when it's Japanese, but not when it's Chinese. If we were to do spec that language dependency,... > > The test uses a web font (Noto CJK) and it's written specifically for that font, without considering other fonts. Noto CJK follows a variation of the convention often used by Adobe fonts (see the [official font readme file](https://github.com/adobe-fonts/source-han-sans/raw/release/SourceHanSansReadMe.pdf) for more details.) But there are surprisingly many other variants that I'm hesitant to spec all those variants. Does that mean that Chrome is effectively depending on the spec's allowance for not trimming in the case of proportional fonts, by considering these characters proportional in the languages where they don't render as full-width? Or something else? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9504#issuecomment-1774250621 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 October 2023 00:30:06 UTC