Re: [charmod-norm] Arabic & Hebrew unique issues associated with sections 2.4 and 2.5

Thanks. I looked at the addition to section 2.5 at: 
http://w3c.github.io/charmod-norm/#legacyCharacterEncoding 
_"..One additional consideration in converting to Unicode is the 
existence of legacy character encodings for bidirectional languages 
that use a visual storage order. That is, unlike Unicode and other 
modern encodings, the characters are stored in memory in the order 
that they are printed on the screen from left-to-right (as with a line
 printer). When converting these encodings to Unicode or when 
comparing text in these encodings, care must be taken to place both 
the source and target text into logical order. For more information, 
see Section 3.3.1 of [CHARMOD]..."_

Overall looks very good. Thanks. Just one minor comment: _".. for 
bidirectional languages..."_ better to say  **for languages with 
bidirectional scripts (such as Arabic or Hebrew)**
This should be also a position of Mati (just for your awareness - we 
worked together for more than 10 years in IBM in the same field. When 
Mati retired I stepped into his big shoes).
Appreciate your attention to my comments. 

-- 
GitHub Notification of comment by tomerm
Please view or discuss this issue at 
https://github.com/w3c/charmod-norm/issues/80#issuecomment-211756775 
using your GitHub account

Received on Tuesday, 19 April 2016 06:35:00 UTC