- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jan 2019 17:40:23 +0000
- To: public-css-archive@w3.org
> Any way, I'm still confused about where (in [7.3. Shaping Across Element Boundaries](https://drafts.csswg.org/css-text-3/#boundary-shaping)) this case, image as a letter, falls : > > 1. Is it "an inline box boundaries" where m/b/p are zero (then nust not break shaping) > or is this : > > 2. an "effective change in formatting" (could break shaping) > > 3. an "impossible shaping across boundaries" ? > > > My guess is 3). Then must break shaping. > If true, I would suggest to add this example at the end of EXAMPLE 22. The box boundaries the spec is talking about are those that "separate two typographic character units". An image is not a typographic character unit. Even if it happens to be an image of a letter. Where the spec talks about shaping across inline boundaries, it is referring to situations where there is text on each side of the boundary (and so there could reasonably be a question as to whether text shaping is continuous across the boundary, or applies separately to the two fragments). In the case of an inline image, there's no question: we have a boundary between text and non-text (image). Images are not text, and do not participate in shaping. So if the desired result is that the text before (and/or after) the image should be shaped as though the image were actually a letter, and participated in shaping (such as cursive Arabic joining), this must be explicitly controlled by the author (using ZWJ to trigger joining forms where appropriate). -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3487#issuecomment-455262117 using your GitHub account
Received on Thursday, 17 January 2019 17:40:25 UTC