- From: Liam Quin via GitHub <sysbot+gh@w3.org>
- Date: Sat, 31 Dec 2022 09:29:20 +0000
- To: public-css-archive@w3.org
white-space-collapse in XSL-FO [1] when true replaces sequences of white space other than linefeed with the first white space in a sequence, so e.g. multiple spaces get turned into a single space everywhere. white-space-treatment in XSL-FO [2] controls whether spaces go away around linefeeds, e.g. including after wrapping. Although XSL-FO is certainly being used, and there are multiple active implementations, i'm not sure how much it matters if CSS itself has a property with a name used by XSL-FO. You could think of XSL-FO as an XML vocabulary that incorporates CSS for styling, though. Because of weird W3C process rules, the XSL-FO spec actually includes a copy of the CSS 2.1 properties, so that it could be published as a Recommendation, but the intent was that they would be the same. However, XSL-FO property values are generally expressions, almost as if they were implicitly surrounded with "calc(...)", so there are limits on how compatible they can be. Antenna House have a product that implements both CSS and XSL-FO, so they might be affected, but, again, in FO mode the values are interpreted differently anyway. A bigger question is whether users would be confused. However, XSL-FO is primarily used in cases where CSS for paged media isn't ready or isn't sophisticated enough, and the stylesheet authors are more likely to cope with the confusion than many other users. I do think it would be better to avoid the confusion if possible, though. It also seems to me that `white-space-collapse` might be confused with margin-collapse, so that `inline-space-collapse` might be better? [1] https://www.w3.org/TR/xsl/#white-space-collapse [2] https://www.w3.org/TR/xsl/#white-space-treatment -- GitHub Notification of comment by liamquin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8273#issuecomment-1368190854 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 31 December 2022 09:29:22 UTC