Re: [css3-writing-modes] Request to publish Last Call Working Draft

On 05/21/2011 01:16 AM, fantasai wrote:
> All right, I'm all out of open issues, aside from the CSS2.1/CSS3WM one
> on nested bidi and breaking inlines across lines [1], which needs to be
> discussed by the WG.
>
> So I'm requesting to publish a Last Call Working Draft of CSS3 Writing
> Modes
> to trigger a wider review by the i18n community.
>
> Here is the latest editor's draft:
> http://dev.w3.org/csswg/css3-writing-modes/
>
> If there are outstanding issues other than [1] that I have not addressed,
> please bring them to my attention.
>
> [1] http://lists.w3.org/Archives/Public/www-style/2011May/0186.html
>
> Thanks,
> ~fantasai
>

I don't think anyone ever responded to my comment on an earlier version, 
at http://lists.w3.org/Archives/Public/www-style/2002Oct/0095.html:

|"non-textual entities such as images are treated as neutral characters,
|unless their 'unicode-bidi' property has a value other than 'normal', 
|in which case they are treated as strong characters in the 'direction'
|specified for the element."
|
|This is not very clear. What cases are intended to have a different
|rendering than that which would result if this phrase were omitted, and
|the image was treated as a neutral character preceded by LRE/RLE
|/LRO/RLO and followed by PDF?
|
|If 'direction' has the value 'rtl', should the image be considered as
|having character type R or AL? Consider the case of an image in Arabic
|text followed by a mathematical formula.
|
|Does this section apply to inline replaced elements with textual
|content, for example form controls?

Back in 2011, I have some questions about the new syntax

  Value: normal | [[ embed | isolate ] || [ plaintext | bidi-override ]]

This seems to permit some combinations that don't make sense, which 
should probably be addressed in the prose.

1) "unicode-bidi: embed bidi-override"

It isn't possible to honor both of these values. Which should win?

2) "unicode-bidi: embed plaintext"

This case is I suppose already covered in the prose, since it's 
specified that "embed" has no effect on elements that are not inline and 
"plaintext" has no effect on inline elements.

See also David Baron's comments at 
https://bugzilla.mozilla.org/show_bug.cgi?id=613149#c5

Received on Monday, 23 May 2011 08:33:16 UTC