Re: I18N-ISSUE-123: Insertion of U+202C [HTML5-prep]

Sorry, I missed this thread until I saw it referenced in last week's conf
call.

> 3.2.6 Requirements relating to bidirectional-algorithm formatting
characters
>
http://www.w3.org/TR/html5/content-models.html#requirements-relating-to-bidirectional-algorithm-formatting-characters

That link leads to badly out-of-date content. The correct link is:
http://dev.w3.org/html5/spec/Overview.html#requirements-relating-to-bidirectional-algorithm-formatting-characters

> Shouldn't there be an explicit statement such as
> "any end tag for a run of phrasing content must be treated
> as if a U+202C had been inserted at that point"

I do not understand the intent. Examples would be useful.

> I suggest to add the following text:
> Bidirectional-algorithm formatting character ranges must be treated
> as if including at their end point as many U+202C (PDF) characters
> as necessary to close any open embeddings and overrides.

This makes an actual requirement on user agents on how they should handle
documents malformed in this respect. That would not be
backwards-compatible, and I am not sure that it's a good idea. The intent
of the bug I filed (https://www.w3.org/Bugs/Public/show_bug.cgi?id=11234)
that led to the referenced section being added to the HTML5 spec was only
to "declare invalid" HTML documents that contain improperly balanced bidi
formatting characters, so that they could be flagged by an HTML validator.

>  <p>[LRE]This is text<b>and[PDF]</b> more text.</p>

I am not sure of the intent of this example from the conf call log, but it
should and does fail the spec's requirements. The LRE is in a text node
that is a child of the <p>, while the PDF is in a text node that is a child
of the <b>. Thus, neither the <p> nor the <b> meets the spec.

Aharon

On Sun, Jul 24, 2011 at 2:36 PM, Matitiahu Allouche <matial@il.ibm.com>wrote:

>  I suggest to add the following text:
>
> Bidirectional-algorithm formatting character ranges must be treated as if
> including at their end point as many U+202C (PDF) characters as necessary
> to close any open embeddings and overrides.
>
>
> Shalom (Regards),  Mati
>           Bidi Architect
>           Globalization Center Of Competency - Bidirectional Scripts
>           IBM Israel
>           Fax: +972 2 5870333    Mobile: +972 52 2554160
>
>
>
>
> From:        Internationalization Core Working Group Issue Tracker <
> sysbot+tracker@w3.org>
> To:        public-i18n-core@w3.org
> Date:        23/07/2011 22:03
> Subject:        I18N-ISSUE-123: Insertion of  U+202C [HTML5-prep]
> Sent by:        public-i18n-core-request@w3.org
> ------------------------------
>
>
>
>
> I18N-ISSUE-123: Insertion of  U+202C [HTML5-prep]
>
> http://www.w3.org/International/track/issues/123
>
> Raised by: Addison Phillips
> On product: HTML5-prep
>
> 3.2.6 Requirements relating to bidirectional-algorithm formatting
> characters
>
> http://www.w3.org/TR/html5/content-models.html#requirements-relating-to-bidirectional-algorithm-formatting-characters
>
> There is one sentence that reads:
>
> --
> However, the use of these characters is restricted so that any embedding
> or overrides generated by these characters do not start and end with
> different parent elements, and so that all such embeddings and overrides
> are explicitly terminated by a U+202C POP DIRECTIONAL FORMATTING character.
> --
>
> Shouldn't there be an explicit statement such as "any end tag for a run of
> phrasing content must be treated as if a U+202C had been inserted at that
> point"
>
>
>
>
>