- From: Eric Muller <emuller@adobe.com>
- Date: Fri, 9 Mar 2012 08:28:13 -0800
- To: "Aharon (Vladimir) Lanin" <aharon@google.com>
- CC: Richard Ishida <ishida@w3.org>, <public-i18n-bidi@w3.org>, Stephen Zilles <szilles@adobe.com>
- Message-ID: <4F5A2F9D.8020300@adobe.com>
Thanks for the answer. I now understand that <br> is really intended to be a paragraph separator, as far as bidi is concerned. I also understand better the relationship between HTML and CSS. I am still a bit confused but before I can express that, a couple of questions: > 'If an inline element is > broken around a bidi paragraph boundary (e.g. if split by a block or > forced paragraph break), then the bidi control codes corresponding to > the end of the element are added before the interruption and the codes > corresponding to the start of the element are added after it. (In > other words, any embedding levels or overrides started by the element > are closed at the paragraph break and reopened on the other side of it.) What does that mean in terms of implementation? - that in the bidi computation, the state after X1-X6 processing of the paragraph before the paragraph boundary is used as the initial state for the X1-X6 processing of the paragraph after that boundary (really, overriding the second X1)? That state being: the current embedding level, the directional status override, the stack of underlying X1-X6. - that only some of that state is carried over? if so, how much? - the meaning is in terms of HTML/CSS only, something like: <span style='direction:d; unicode-bidi:u'>...<br>...</span> is equivalent to: <span style='direction:d; unicode-bidi:u'>...<span><br><span style='direction:d; unicode-bidi:u'>...</span> (with the property present on the second only if it is present on the first; and of course, with the similar treatment of relevant HTML elements attributes). If that is the case, what are the exact rules? - something else? Also, what is the eor of the last run of the paragraph before, and the sor of the first run of the paragraph after? Thanks, Eric.
Received on Friday, 9 March 2012 16:28:49 UTC