- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Mar 2025 16:26:16 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-text-4] [text-autospace] Spacing across element boundaries for BiDi content`, and agreed to the following: * `RESOLVED: autospacing happens *after* bidi-reordering, and we'll add a complex example to the spec` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: so text-autospace inserts spaces between "changes" in a script<br> <TabAtkins> fantasai: if you ahve chinese with a little englihs, there should be some gap around the english otherwise it feels cramped<br> <TabAtkins> fantasai: q is what to do with bidi text<br> <TabAtkins> fantasai: we dont' insert space between chinese text and a *symbol*, only between chinese text and a letter<br> <TabAtkins> fantasai: so if you had a stretch of rtl text, like hebrew that ends with a symbol<br> <TabAtkins> fantasai: and you give it a direction so it all flips<br> <TabAtkins> fantasai: so symbol is on the left, hebrew letters on the right<br> <TabAtkins> fantasai: chinese text before and after<br> <TabAtkins> fantasai: if you insert space before reordering, you'll put it on the left side, which ends up between the chinese text and the symbol, while the hebrew and chinese dont' get a space<br> <TabAtkins> fantasai: so correct answer is to manage the sapce in visual order, after bidi reordering<br> <TabAtkins> fantasai: this is challenging, it interacts with linebreaking in awkward ways. hard to get perfectly right without maybe some backtracking<br> <TabAtkins> fantasai: so i think th e correct answer is visual spacing<br> <TabAtkins> fantasai: for practicual purposes, might tolerate getting it wrong in some complex cases<br> <TabAtkins> florian: do we need to spec the allowance for getting it wrong?<br> <TabAtkins> florian: or jsut spec the right thing and expect people to get it wrong sometimes, but they should still try?<br> <TabAtkins> fantasai: i'm not sure<br> <TabAtkins> fantasai: i think it's important to maek sure we get right - if both sides require spacing, it's done correctly, never get double space on one side<br> <TabAtkins> fantasai: that's minimum bar<br> <TabAtkins> astearns: I think we should specify what we want to see, without allowance, and only do that "getting it wrong is allowed" part if we have to<br> <TabAtkins> fantasai: i think that's reasonable.<br> <TabAtkins> fantasai: if authors are running into problems with certain cases, they can complain, and then we'll know those cases matter.<br> <TabAtkins> astearns: so proposed resolution is we specify that autospacing is done after bidi reordering<br> <TabAtkins> astearns: and you should never double auto-space any side<br> <TabAtkins> fantasai: yeah, that's implied<br> <TabAtkins> florian: do we want to add a note about it being hard?<br> <fantasai> Scribe+<br> <fantasai> TabAtkins: Useful to acknowledge if something is significantly difficult<br> <fantasai> TabAtkins: Here be dragons, when implementing<br> <TabAtkins> fantasai: i think they'll notice<br> <TabAtkins> astearns: would be good to have at least one example, hopefully we can find a real-world example<br> <TabAtkins> florian: could have a note which is less silly than my earlier phrasing. "CSSWG acknowledge that the interactino of this with line-breaking may be challenging to implement"<br> <TabAtkins> fantasai: or literally say "here be dragons"<br> <fantasai> s/or literally/or, as bkardell suggests, literally/<br> <TabAtkins> astearns: [restates proposed reoslution]<br> <TabAtkins> RESOLVED: autospacing happens *after* bidi-reordering, and we'll add a complex example to the spec<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10803#issuecomment-2718448731 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 March 2025 16:26:17 UTC