- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 26 Apr 2012 20:32:53 +0000 (UTC)
- To: "Aharon (Vladimir) Lanin" <aharon@google.com>
- cc: public-texttracks@w3.org
On Thu, 26 Apr 2012, Aharon (Vladimir) Lanin wrote: > > Thanks, this is great! > > One thing, though. As far as I can see, the WebVTT spec does not say > that the cue is supposed to be *rendered* in accordance with the Unicode > bidi algorithm, and more specifically that its P3 (i.e. first strong > character) determines each paragraph's base direction. (Currently, the > spec mentions the bidi algorithm's paragraph level steps effectively > just for the purpose of resolving cue alignment. It does not say > anything about the rendering, i.e. visual ordering of the characters.) > The bidi algorithm allows higher level protocols to override P3, as is > the case almost everywhere in HTML, for example. It is important that > implementers realize that in WebVTT there is no higher level protocol, > and thus P3 should apply, and (bidi-aware) users know what to expect and > how they can make use of it. The rendering is defined in terms of CSS. CSS is the higher level protocol and it is CSS that then invokes the bidi algorithm for layout. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 26 April 2012 20:33:18 UTC