- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Oct 2024 11:55:27 +0000
- To: public-css-archive@w3.org
> Yes, in my opinion: the natural expectation would be that any character or sequence that displays an emoji-style glyph by default should change to a text-style glyph if font-variant-emoji: text is applied. The issue is how would such sequences be encoded in a font? Inserting VS15 would make the sequences non RGI sequences. We're currently looking into sequences support in our Noto Emoji (non-color) font. Are there any other known monochromatic fonts that would have support for sequences? > So in the case of 🐈‍⬛, applying font-variant-emoji: text does not insert an actual U+FE0E codepoint and break the sequence (resulting in a text-style cat, perhaps as a line-drawing or outline, followed by a black square); it's still an emoji sequence requesting a black cat, but now it's supposed to be a text-style black cat rather than an emoji-style one. The way I read the spec: https://www.w3.org/TR/css-fonts-4/#valdef-font-variant-emoji-text for **text**: "Code points are rendered as if U+FE0E VARIATION SELECTOR-15 was appended to every Presentation Participating Code Point." this means it would virtually insert VS15 after cat and break the sequence into a non RGI sequence. In any case, we are back at what is the encoding the font and how do we differentiate a color from a non-color encoding for ZWJ sequences. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11036#issuecomment-2429078282 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 October 2024 11:55:28 UTC