Re: [svgwg] tspan and text shaping (#634)

The SVG Working Group just discussed `tspan and text shaping`.

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> Topic: tspan and text shaping<br>
&lt;krit> GitHub: https://github.com/w3c/svgwg/issues/634<br>
&lt;krit> See discussions on https://github.com/w3c/svgwg/issues/635 for details<br>
&lt;krit> AmeliaBR: previous resolution to BIDI and harominzing with CSS Text does cover this issue.<br>
&lt;krit> AmeliaBR: CSS guidance has more nuances<br>
&lt;chris> I think that was the best we could assume, *at the time*<br>
&lt;krit> AmeliaBR: Harminizing means we drop the rule that any markup boundaries disables ligatures<br>
&lt;krit> s/Harminizing/Harmonizing/<br>
&lt;krit> AmeliaBR: some cases might not be defined specifically at the end. CSS ends up with auto a lot.<br>
&lt;krit> AmeliaBR: Should it be possible to paint half of the ligature in another color than the other? Firefox does it.<br>
&lt;krit> AmeliaBR: it divides the offset distances in half<br>
&lt;krit> Tav: this may cause trouble for more complicated glyphs<br>
&lt;krit> myles: agree.<br>
&lt;krit> myles: anything like that is too complicated.<br>
&lt;krit> Tav: we wouldn't implement it<br>
&lt;krit> AmeliaBR: what should happen?<br>
&lt;krit> AmeliaBR: what if the color is dynamic on selection?<br>
&lt;krit> myles: I would prefer to leave this up to the implementation. Firefox behaviour shouldn<br>
&lt;krit> t  be illegal but wouldn't want to implement it. So spec should not dictate one or the other way.<br>
&lt;krit> krit: need to resolve?<br>
&lt;krit> AmeliaBR: maybe we tie this into CSS Text<br>
&lt;krit> myles: if this WG thinks one behavior is better than the other, CSS should do the same.<br>
&lt;krit> krit: does sound like we don't need another resolution. We would do what ever CSS does.<br>
&lt;krit> krit: this is covered by harmonising resolution.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/634#issuecomment-494145064 using your GitHub account

Received on Monday, 20 May 2019 20:47:35 UTC