W3C home > Mailing lists > Public > public-html@w3.org > March 2010

Re: FPWD of Additional Requirements for Bidi in HTML

From: Matitiahu Allouche <matial@il.ibm.com>
Date: Mon, 8 Mar 2010 19:37:05 +0200
To: Maciej Stachowiak <mjs@apple.com>
Cc: Richard Ishida <ishida@w3.org>, Philippe Le Hegaret <plh@w3.org>, public-html@w3.org, public-i18n-core@w3.org, public-i18n-core-request@w3.org, Sam Ruby <rubys@intertwingly.net>
Message-ID: <OFBA9D2FC1.96ED037C-ONC22576E0.005F4E84-C22576E0.0060C7CF@il.ibm.com>
I have no W3C official status, but I am one of the co-authors of the 
proposal. I think that I represent this group when I assure you that it 
has never been our intention to write a separate specification or to do 
anything to jeopardize the HTML5 WG's work.

On the contrary, considering that the HTML5 WG may not have enough time to 
dedicate to Bidi matters, which are not always simple, we have tried to 
gather an informal group of Bidi experts to elaborate a well-enough cooked 
proposal, to be eventually delivered at the door-step of the HTML5 WG.

Although good progress has been made, we would prefer to have a little 
more "cooking" time before deciding that the document is ready for HTML5 
examination. This is just to save the HTML5 WG members some effort. 
Whoever wants to participate in the discussion starting now is definitely 
welcome.

Only my 2 cents.

Shalom (Regards),  Mati
           Bidi Architect
           Globalization Center Of Competency - Bidirectional Scripts
           IBM Israel
           Phone: +972 2 5888802    Fax: +972 2 5870333    Mobile: +972 52 
2554160




From:
Maciej Stachowiak <mjs@apple.com>
To:
Sam Ruby <rubys@intertwingly.net>
Cc:
Richard Ishida <ishida@w3.org>, public-html@w3.org, 
public-i18n-core@w3.org, Philippe Le Hegaret <plh@w3.org>
Date:
08/03/2010 03:30
Subject:
Re: FPWD of Additional Requirements for Bidi in HTML
Sent by:
public-i18n-core-request@w3.org




On Mar 7, 2010, at 10:09 AM, Sam Ruby wrote:

> Maciej Stachowiak wrote:
>> Hi Richard and I18N WG,
>> On Mar 5, 2010, at 3:29 AM, Richard Ishida wrote:
>>> HTML folks,
>>>
>>> Just to let you know the expectations of the i18n WG wrt this 
>>> document[1] which was published yesterday.  We do not expect the 
>>> HTML WG to review and comment on it just yet.
>>>
>>> The document is still in early draft, and was published to 
>>> facilitate ongoing feedback from bidi experts and i18n folks. It 
>>> also contains some explicitly identified open issues.
>>>
>>> The plan is to obtain feedback as soon as possible from bidi 
>>> experts and internationalization folks, then issue a new draft 
>>> that incorporates the results of those discussions.  Only at that 
>>> point do we plan to put the proposals to the HTML community and 
>>> seek their comments and commitment. Depending on the amount of 
>>> discussion that takes place, we would hope to publish the second 
>>> draft in about a month from now.
>>>
>>> [1] http://www.w3.org/TR/2010/WD-html-bidi-20100304/
>> It's a little quirky to deliver feedback on the HTML WG's 
>> deliverables in the form of a Working Draft developed elsewhere, 
>> and it might have been better to make us more aware of this effort 
>> ahead of time. (I, for one, was surprised to see  seventh Working 
>> Draft published with ours and was puzzled that I hadn't seen it 
>> before.)
>
> I don't believe that it has been established that bidi is an HTML WG 
> deliverable.  All that I have seen stated is "Seven Documents 
> Related to HTML Published".
>
> http://www.w3.org/News/2010#entry-8735

I don't think this *draft* is established as an HTML WG deliverable. 
However, the draft suggests possible changes to HTML, rather than 
itself defining conformance requirements. My assumption is that 
there's a desire to put these changes in the HTML spec itself, not to 
convert to a document to a standalone spec that defines its own 
separate conformance requirements. Perhaps Richard could clarify.

Also, HTML5 already defines many markup features for bidi support in 
particular and international text in general. It's clearly in scope.

>
>> That being said, as long as the HTML WG gets the feedback in the 
>> end, I'm not too concerned with the process of developing it.
>
> I would modify that statement: as long as the groups are working 
> together, I'm not concerned about which group publishes it.

I would be concerned if the end result is two specs with contradictory 
conformance requirements, without even an attempt to fix the HTML5 
spec itself.

>
>> From reading over this draft, it seems to me that most of this 
>> feedback is ready to be delivered to the HTML WG right now. I see 
>> many specific points that identify a specific problem in great 
>> detail, outline why the current state of the spec doesn't work, and 
>> propose at lest one workable solution. That's more than enough data 
>> to go into a bug report.
>> I would expect that bug reports on these issues would most likely 
>> resolved expeditiously to everyone's satisfaction, and without any 
>> great controversy. The only potential problems I see are with 
>> details of syntax(*). I think those are best resolved within the 
>> HTML WG. I also suspect some of the comments may be issues for CSS, 
>> not HTML, for example the treatment of list markers. HTML 
>> completely defers to CSS on list rendering. Either way, it would be 
>> good to identify those kinds of issues ASAP rather than continuing 
>> to develop in a silo.
>> If the I18N WG would like these issues addressed before Last Call, 
>> I strongly recommend delivering the feedback to the HTML WG as soon 
>> as possible, ideally in the form of bug reports, one per distinct 
>> issue.
>
> Against which component would such bugs be filed?

"HTML5 spec bugs".

> What I see published for bidi seems to meet the criteria for a 
> vendor-neutral applicable specification, as described by section 
> 2.2.2 of the HTML5 Working Draft.

Maybe I am misunderstanding the draft, but it looks to me like it is 
requesting changes to HTML, not attempting to be its own separate 
specification. Let's take a specific example. The draft suggests that 
<br> should act as a bidi separator. HTML5 specifically says it should 
*not* act as a bidi separator (as does HTML4). It seems logical that 
the intent here is to fix HTML5, not to have a separate spec with a 
directly contradictory processing requirement.

My interpretation of the intent of this document seems to be in 
accordance with the subsequent note from Addison Phillips.

Really all I'm saying is that *if* the I18N WG wants this document to 
result in changes to HTML5, they should try to deliver the relevant 
feedback to the HTML WG as soon as possible. Richard's original note 
was that I18N WG plans to wait at least a month before making any 
proposals to the HTML WG or seeking feedback.

Regards,
Maciej
Received on Monday, 8 March 2010 17:37:45 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:59 UTC