- From: Glenn Adams <glenn@skynav.com>
- Date: Tue, 17 May 2011 22:19:02 -0600
- To: Cameron McCormack <cam@mcc.id.au>
- Cc: Alex Danilo <alex@abbra.com>, public-svg-wg@w3.org
- Message-ID: <BANLkTin9nxsT-u7-GakP0RXtvzFr94SejQ@mail.gmail.com>
I expect that "base writing direction" is intended to be equivalent to "paragraph embedding level" as used by UAX#9, so it sort of says it in what you cite below. G. On Tue, May 17, 2011 at 10:14 PM, Cameron McCormack <cam@mcc.id.au> wrote: > Glenn Adams: > > Perhaps Batik is not correctly assigning the paragraph embedding level. > > Since SVG doesn't have a paragraph construct per se, I would expect the > > direction property on the <text/> element to determine the paragraph > > embedding level. In Cameron's example, that was "rtl", which would make > the > > paragraph embedding level 0, not 1. > > Just a quick note to say that I believe that’s the intention: that > <text> is treated like a block level element, and direction:rtl should > affect the paragraph embedding level, while for direction to have any > effect on <tspan>s unicode-bidi:bidi-override would be required. > > http://www.w3.org/TR/SVG/text.html#DirectionProperty says: > > This property specifies the base writing direction of text and the > direction of embeddings and overrides (see ‘unicode-bidi’) for > the Unicode bidirectional algorithm. For the ‘direction’ property > to have any effect on an element that does not by itself establish > a new text chunk (such as a ‘tspan’ element without absolute > position adjustments due to ‘x’ or ‘y’ attributes), the > ‘unicode-bidi’ property’s value must be embed or bidi-override. > > which doesn’t explicitly state that <text> is to be considered the > paragraph, but I think it makes sense. > > -- > Cameron McCormack ≝ http://mcc.id.au/ >
Received on Wednesday, 18 May 2011 04:19:50 UTC