W3C home > Mailing lists > Public > www-i18n-comments@w3.org > March 2004

RE: New Tutorial: Character sets & encodings in XHTML, HTML and CSS

From: Richard Ishida <ishida@w3.org>
Date: Thu, 25 Mar 2004 10:18:02 -0000
To: "'Matitiahu Allouche'" <matial@il.ibm.com>
Cc: <www-international@w3.org>, <www-i18n-comments@w3.org>
Message-ID: <001e01c41252$753a26a0$6801a8c0@w3cishida>

Hello Mati,

Many thanks for your very helpful comments.  See my replies below...

> -----Original Message-----
> From: www-i18n-comments-request@w3.org
> [mailto:www-i18n-comments-request@w3.org] On Behalf Of 
> Matitiahu Allouche
> Sent: 25 March 2004 08:09
> To: Richard Ishida
> Cc: www-international@w3.org; 
> www-international-request@w3.org; www-i18n-comments@w3.org
> Subject: Re: New Tutorial: Character sets & encodings in 
> XHTML, HTML and CSS
> 
> 
> 
> A few comments.  Sorry that they are mostly nitpickings.

I much prefer that to major substantive disagreements ;-)  Actually these
are all very helpful. Thanks.


> 
> 1) Section "Character escapes" mentions &#x597D; as the
> escape for the 
> Hebrew letter Alef.  I don't know how this value was 
> obtained, U+597D is 
> not a defined Unicode character.  The right escape IMHO 
> should be &#x05D0.

&#x597D; is the kanji character in the table nearer the top of the page.
Thanks for spotting the incorrect mention related to aleph. Fixed.


> 
> 2) In section "Consider using a Unicode encoding", instead of
> "Unicode encodings support many languages with a single 
> encoding across 
> all pages and forms, regardless of language."
> I suggest
> "All Unicode encodings support many languages and can 
> accomodate all kinds 
> of pages and forms containing any mixture of those languages."

Changed to:
A Unicode encoding can support many languages and can accommodate pages and
forms in any mixture of those languages. Its use also eliminates...


> 
> 3) In section "When to do this" following mention of the IANA
> registry, 
> add "are" after "there" in "there no disadvantages".

Fixed.


> 
> 4) In section "Precedence rules", add "is" after "it" in "since it
> likely".

Fixed.


> 
> 5) In the title "entities and numeric charater references
> (ncrs)", the 
> acronym should  be spelled "NCRs", to be coherent with further 
> occurrences, and to distinguish the plural "s" from the 
> acronym itself.

Fixed. Thanks.


> 
> 6) In the next paragraph, "are way" should be "are ways".

Fixed.


> 
> 7) The example for CSS escape is *not* terminated by a space, despite
> stating in the previous line that it should be.

Mmm. Ok fixed.


> 
> 8) In section "When to use escapes", the sentence "For example, to
> represent Chinese characters in an ISO Latin 1 document." is not a 
> complete sentence, and should be an added clause to the 
> previous sentence 
> (separated by comma).

Fixed.


> 
> 9) In the table contained in section "Other Unicode
> characters are OK", 
> LRM and RLM are commented as "Deprecated in Unicode".  I am very 
> surprised.  What is the basis for such a statement?

Oh dear.  I guess that crept in via copying of tables.  Fixed!


> 
> 10) In section "Compatibility characters vary in
> appropriateness, add a 
> comma before "in some other cases it denotes a property".

Fixed.


Cheers (Regards),
RI


> 
> 
> Shalom (Regards),  Mati
>            Bidi Architect
>            Globalization Center Of Competency - Bidirectional Scripts
>            IBM Israel
>            Phone: +972 2 5888802    Fax: +972 2 5870333    
> Mobile: +972 52
> 554160
> 
> 
> 
> 
> 
> "Richard Ishida" <ishida@w3.org>
> Sent by: www-international-request@w3.org
> 24/03/2004 14:44
> 
> To
> <www-international@w3.org>
> cc
> 
> Subject
> New Tutorial: Character sets & encodings in XHTML, HTML and CSS
> 
> 
> 
> 
> 
> The GEO task force has published its first tutorial:
> 
>                  Character sets & encodings in XHTML, HTML and CSS
> 
> At: http://www.w3.org/International/tutorials/tutorial-char-enc.html
> 
> 
> This tutorial has been worked on for quite some time by the
> GEO Task Force 
> of the W3C Internationalization Working Group, and it is 
> thought to be 
> ready for publication. For an undetermined initial period we 
> will leave 
> the status as Draft to indicate that we invite feedback on 
> the document.
> 
> 
> You can find links to internationalization specifications,
> FAQs, articles, 
> tools, tests, and soon tutorials at http://www.w3.org/International/
> 
> ============
> Richard Ishida
> W3C
> 
> contact info: http://www.w3.org/People/Ishida/
> 
http://www.w3.org/International/ 
Received on Thursday, 25 March 2004 05:18:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:32:34 GMT