- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Oct 2018 20:24:21 +0000
- To: public-svg-issues@w3.org
The SVG Working Group just discussed `Update on character counting for layout attributes on text/tspan elements`, and agreed to the following: * `RESOLUTION: Keep unicode code point for now until we get feedback from implementers. Keep previous resolution.` <details><summary>The full IRC log of that discussion</summary> <krit> topic: Update on character counting for layout attributes on text/tspan elements<br> <krit> krit: Tav, saw you discussed on the mailing list?<br> <krit> Tavmjong: got a response. He said you can get the breaking points from pango. Still not sure if that is the easiest way to do. He wants to avoid the CSS wording because that depends on context.<br> <krit> Tavmjong: The spec says that breaking may depend on context. So you'd break at different points. Unicode might work but I'd not say this is the way to go.<br> <krit> krit: would you approve if we use CSS and ask to clarify what context awareness means?<br> <krit> Tavmjong: if we have.a set of numbers that need to apply to the same groups of chars. And CSS3 it depends on the context.<br> <krit> krit: it'd be great to understand what the context is<br> <krit> AmeliaBR: we had this issues with white space collapsing.<br> <krit> Tavmjong: In the email says that he likes the Edge behavior better with the cluster selection. Pango returns an array that are well defined clusters in unicode.<br> <AmeliaBR> Behdad's reply: https://lists.w3.org/Archives/Public/www-svg/2018Sep/0018.html<br> <krit> Tavmjong: if we are to switch from unicode code points, it would be the thing to switch too.<br> <krit> krit: could it happen that :first-letter selector can have a different meaning on layout and rendering?<br> <krit> AmeliaBR: :first-letter has a different set of settings.<br> <krit> AmeliaBR: for layout it is a different and predictability is more important.<br> <krit> Tavmjong: my suggestion would be to leave unicode code points and add a note with a request of comments from implementers.<br> <krit> AmeliaBR: the limitation of leaving would be the inconsitencies and we can not file bugs on browsers until we decided how to go forward.<br> <krit> krit: The CSS has more text experts... is that something we should bring it up there or is it completely independent of CSS and its definition of typographic characters?<br> <krit> Tavmjong: I think it is independent. We can not use typographic chars from CSS since you might break at different positions dependent on the context. That would be unpredictable and not consistent.<br> <krit> Tavmjong: so either use code points or Edge's behavior of clusters. (which is not known detaul)<br> <krit> s/detaul/detail.<br> <krit> chris: surrogates are in UTF16 and 2 sets allow defining one character and older implementations do not understand this<br> <krit> AmeliaBR: this is how we even got into it<br> <krit> Tavmjong: only FF supports this but no one else.<br> <krit> AmeliaBR: we are going to file issues against specs. We need to decide on it to fix other issues.<br> <AmeliaBR> github: https://github.com/w3c/svgwg/issues/537<br> <chris> https://en.wikipedia.org/wiki/UTF-16#U+10000_to_U+10FFFF<br> <krit> krit: Maybe going with Tavs proposal and ask for browser input would unblock us for now.<br> <krit> krit: How can we bring this to their attention?<br> <krit> AmeliaBR: Tav, could you go though the text that may need changes and show how it would affect output if we are going to change?<br> <krit> Tavmjong: I can create a PR with the changes.<br> <krit> RESOLVE: Keep unicode code point for now until we get feedback from implementers. Keep previous resolution.<br> <krit> RESOLUTION: Keep unicode code point for now until we get feedback from implementers. Keep previous resolution.<br> <krit> AmeliaBR: Can it handle multi Byte characters and can it handle the 2nd issue?<br> <krit> chris: both do not affect western text<br> <krit> Tavmjong: emoji is a good example<br> <chris> s/do not/*do*<br> <krit> Tavmjong: some emojis use colors?<br> <krit> chris: exactly, you may need to combine characters.<br> <krit> Tavmjong: maybe w good way to test<br> <krit> s/maybe w/maybe a/<br> <krit> Tavmjong: chris, could you send me an example with emojis? Then I'd create a test out of it.<br> <krit> chris: yes<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/svgwg/issues/537#issuecomment-426049945 using your GitHub account
Received on Monday, 1 October 2018 20:24:22 UTC