Re: [csswg-drafts] [css-writing-modes-3] Propose to replace "'text-orientation: upright' to cause strong LTR" with author notes how to do it

> I agree upright Hebrew appear top-to-bottom, but less sure about 
how. Complex cases are like:

    <div class=U><span dir=rtl>ABC</span></div>

> The "ABC" is still strong LTR, correct?

Yes, I think so; and so it appears as

    A
    B
    C

in top-to-bottom order.

    <div class=U>
      ABC
      <span class=R>DEF</span>
      GHI
      <span class=R>JKL</span>
      MNO
    </div>
> 
> The "DEF" and "JKL" are RTL so reordering occurs, as "ABC LKJ GHI 
FED MNO", correct?

I'm not sure I understand you here, or perhaps I disagree. The 
characters "DEF" and "JKL" are RTL and so will reorder to "FED" and 
"LKJ" respectively; but I don't expect them to swap places within the 
overall-LTR (top-to-bottom) line of text. So the visual result (using 
lowercase to stand in for glyphs that are rotated 90° clockwise) 
should probably be:

    A
    B
    C
    f
    e
    d
    G
    H
    I
    l
    k
    j
    M
    N
    O

Does that make sense to you?
 
    <div class=R>
      ARABIC TEXT HAS
      <span class=U>SYMBOL1</span>
      AND
      <span class=U>SYMBOL2</span>
      IN A PARAGRAPH.
    </div>

> The two symbols are strong LTR so reordering occurs, making 
"SYMBOL2" visually earlier than "SYMBOL1", correct?

Again, I don't think the SYMBOL1 and SYMBOL2 spans will swap places 
within the overall-RTL paragraph. The ARABIC TEXT... as a whole will 
run bottom-to-top, so SYMBOL1 will appear (upright, and top-to-bottom 
if it has multiple characters) first (lower down in the line), and 
SYMBOL2 will appear higher:

    .
    .
    .
    a
    r
    a
    p

    a

    n
    i

    S
    Y
    M
    2

    d
    n
    a

    S
    Y
    M
    1

    s
    a
    h

    c
    i
    b
    a
    r
    a

(abbreviating your example a bit to save space). Reasonable?

-- 
GitHub Notification of comment by jfkthame
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/755#issuecomment-265793446 
using your GitHub account

Received on Thursday, 8 December 2016 16:59:56 UTC