- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Nov 2018 06:40:32 +0000
- To: public-svg-issues@w3.org
As far as I understood, @r12a, @Tavmjong and @fantasai support unicode code points because they are more robust and stable. The preferred output on the other side would be what Edge does. Which is closer to EGCs but we are not sure about that. @litherum and @kojiishi support the latter approach. Even if the output might change/get corrected over time. I didn't see many authoring tools using multiple values for `x`, `y`, `dx` or `dy`. So maybe we can assume that current content get hand edited for the most part? For hand edited content, do we expect that stability is more important than the semantic correctness? Given that authors went to the effort to actually align the "chars" correctly? Note that Chrome/WebKit seem to do char mapping by unicode code points for interfaces like `getNumberOfChars()` as well. (Even though it is not what is currently speced.) For hand edited content it might be better if those align? It would be great if we can get to a compromise on this issue and be able to close it. -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/svgwg/issues/537#issuecomment-437773017 using your GitHub account
Received on Monday, 12 November 2018 06:40:33 UTC