W3C home > Mailing lists > Public > www-international@w3.org > July to September 2009

Re: Updated Working Draft: Best Practices for Authoring HTML: Handling Right-to-left Scripts

From: Matitiahu Allouche <matial@il.ibm.com>
Date: Fri, 24 Jul 2009 01:13:56 +0300
To: "Richard Ishida" <ishida@w3.org>
Cc: www-international@w3.org, www-international-request@w3.org
Message-ID: <OF78356B38.EDAA6FB6-ONC22575FC.0051BE04-C22575FC.007A1FF6@il.ibm.com>
A few comments, most of them editorial, where "=>" means "should be 
replaced by".

1) In section 1.2, "amout" => "amount"

2) In 1.2.1, "they way" => "the way", "see read" => "read"

3) In 1.2.2, there is a singular reference to a "Get more information" 
link, but the next sentence uses a plural reference "These will link".

4) In 1.4, "The opposite of a block element is a block element" => "The 
opposite of an inline element is a block element"

5) In 2.1,  'Bidirectional', or 'bidi', text typically refers to text 
written using a mixture of right-to-left and left-to-right text.
Text is not written using text.  Maybe it should be "using a mixture of 
right-to-left and left-to-right scripts".

6) In 2.1, "it's examples" => "its examples"

7) In 2.1, "Pheonician" => "Phenician" ?

8) In 3.1, I suggest "the overall context of your editor" => "the base 
direction of the editing window in your editor"
In general, I suggest to replace mentions of "context" or "overall 
context" throughout the document by "direction" or "base direction", 
because "context" is a fuzzy notion without a well defined meaning for the 
subject at hand, while "direction" is easily translatable to HTML or CSS 
keywords.

9) In 3.1 Example 2,
<p/>[paragraph_content]<"[title_value"=p class="myclass" title>.
should be (missing bracket):
<p/>[paragraph_content]<"[title_value]"=p class="myclass" title>.

10) In 3.2, the numeric equivalent for &rlm; must be &#x200F (and not 
&#x200E, which is the equivalent of &lrm;).
Same thing for 2 references in the explanation text of Example 5 and 3 
references in the yellow window of Example 5.

11) In 3.2 Example 5, "the escape fragments to appear" => "the escape 
fragments will appear"

12) In section 5 and Best Practice 3, I suggest to use "page" rather than 
"document", because this is more precise.

13) In section 5, Best Practice 3, Discussion: "browser chrome" is not a 
widely understood term, especially for Internet Explorer users.

14)  In section 5, Best Practice 4, Discussion: saying that "Visually 
ordered bidirectional HTML does not conform to the HTML specification" may 
be too strong.  The BDO tag handles visually ordered bidirectional text.

15) In section 5, Best Practice 4, Discussion: "flowing text that 
automatically wrap" => "flowing text that automatically wraps"

16) In Best Practice 4, ISO code pages:  "all characters in memory in the 
order in which it would normally be typed" => "all characters in memory 
are stored in the order in which they would normally be typed"

17) In Best Practice 4, ISO code pages: either do not mention ISO-8859-e 
or add a note that it is not supported by any common browser.

18) In Best Practice 5, the title "Don't use CSS styling for HTML" is 
misleading: it is only for specifying direction that CSS styling should be 
avoided.

19) In Example 10, it is not clear why some, and not all, of the lines 
with Arabic text are right-aligned.

20) In Example 13, "This is what we should have seen. the key to web 
standards" => "This is what we should have seen."

21) In the following note, "Best Practice XX" => "Best Practice <some real 
number>"

22) In the next sentence, "you are probably more likely encounter" => "you 
are more likely to encounter"

23) In Example 15, "This is what we should have seen is this." => "This is 
what we should have seen."

24) At the end of Example 15:  "which associates it" => "which associates 
them"

25) After Example 16, "because of the likelihood" => "because of the small 
likelihood"

26) In Example 17, "To solve the problem we add a LRM character" => "To 
solve the problem we add a RLM character"


These are my comments up to Example 17.  I will add some comments on the 
rest of the document some time soon,


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




"Richard Ishida" <ishida@w3.org> 
Sent by: www-international-request@w3.org
15/07/2009 16:06

To
<www-international@w3.org>
cc

Subject
Updated Working Draft: Best Practices for Authoring HTML: Handling 
Right-to-left Scripts






http://www.w3.org/TR/i18n-html-tech-bidi/

The Internationalization Core Working Group has published an updated 
Working Draft of Best Practices for Authoring HTML: Handling Right-to-left 
Scripts.

This document provides advice for the use of HTML markup and CSS style 
sheets to create pages containing languages that use right-to-left 
scripts, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.

NOTE: The Working Group believes this document is complete and does not 
anticipate any substantive changes. This draft is provided as a last 
chance for review and feedback before publication as a Working Group Note.

Please send comments on this document to www-international@w3.org by 28 
July 2009.

RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/
Received on Thursday, 23 July 2009 22:14:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 July 2009 22:14:44 GMT