- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Nov 2018 02:02:32 +0000
- To: public-svg-issues@w3.org
> * Use code points for counting, because they are stable and pairing must remain stable. This gives us both forwards and backwards compatibility (except for surrogate pairs, which would not be backwards-compatible). > * UAs (may/must?) ignore coordinates associated with combining characters (i.e. not the base character) in any typographic character unit. This is defining a new type of Unicode segmentation, which should be done in Unicode, not CSS. Web engines should not be in the business of defining their own segmentation types, because Web engines are not the only software with forward-compatibility concerns. My intuition is that a segmenter that's just like code points except for combining characters would be too naive. Bringing this to Unicode would get the necessary domain experts to provide feedback on this type of segmenter. The most obvious counter-example is the family emoji, but I will do some additional research determine the relationship between this new segmenter type and EGCs. > SVG already has rules for font-specific combined characters Neither code points, nor EGCs, nor this new segmentation type are font-dependent. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/svgwg/issues/537#issuecomment-435247211 using your GitHub account
Received on Friday, 2 November 2018 02:02:33 UTC