W3C home > Mailing lists > Public > public-i18n-geo@w3.org > June 2005

Feeback on tutorials

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 02 Jun 2005 01:59:29 +0900
Message-ID: <429DE971.7030503@w3.org>
To: GEO <public-i18n-geo@w3.org>

Hi Richard,

Here is some feedback on the Bidi Tutorial:

- "With logical ordering text is stored in memory in the order in which 
it would normally be typed (and usually pronounced)": Delete "(and 
usually pronounced)", because the relation of characters to 
pronounciation is rather weak (except for IPA or SAMPA).
- "Putting markup around the comma is a bit like cracking an egg with a 
hammer in this case.": That's great!
- "they create states with invisible boundaries": you should explain 
"states".
- "CSS provides properties to specify bidirectional behaviour." You 
should say s.t. about the CSS version.


Here is some feedback on the Tutorial about Multilingual Web Addresses:

- "Various document formats already support IRIs. Examples include HTML 
4.0, XML (system identifiers), the XLink href  attribute, XML Schema's 
anyURI datatype,": Unfortunately this is not true, as I had to realize 
myself while reviewing QT: anyURI does not support IRI directly yet, it 
still refers to XLink 1.0

- "Unfortunately, not so many protocols allow IRIs to pass through 
unchanged.": Why unfortunately? The mapping from IRI to URI is 
reversible, and the protocols you mention have good reasons for the 
ASCII-escaping; the IRI spec itself mentions HTTP:  "The intent is not 
to introduce IRIs into contexts that are not defined to accept them.  
For example, XML schema [XMLSchema] has an explicit type "anyURI" that 
includes IRIs and IRI references. Therefore, IRIs and IRI references can 
be in attributes and elements of type "anyURI".  On the other  hand, in 
the HTTP protocol [RFC2616], the Request URI is defined as a URI, which 
means that direct use of IRIs is not allowed in HTTP requests. "
- "Normalization involves such things as converting uppercase characters 
to lowercase, reducing alternative representations (eg. converting 
half-width kana to full), eliminating prohibited characters (eg. 
spaces), etc.": Do you want to say s.t. about the various normalization 
forms, esp. C??

That's it!

Hear you in a minute,

Felix
Received on Wednesday, 1 June 2005 16:59:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:02 UTC