W3C home > Mailing lists > Public > www-international@w3.org > October to December 2007

RE: I18N issues for Widgets Spec [Was: Re: [Widgets] ASCII File names - request for comments]

From: Richard Ishida <ishida@w3.org>
Date: Tue, 4 Dec 2007 17:01:08 -0000
To: "'Uma Umamaheswaran'" <umavs@ca.ibm.com>, "'Marcos Caceres'" <marcosscaceres@gmail.com>
Cc: "'Arthur Barstow'" <art.barstow@nokia.com>, <public-appformats@w3.org>, <public-i18n-core@w3.org>, "'Thomas Roessler'" <tlr@w3.org>, <www-international@w3.org>
Message-ID: <017a01c83697$447ec760$6401a8c0@rishida>

I agree that the WAF WG should make representations to Apple to fix the
MacOS issue, and not just try to find wording for the spec that gets us
around the problem.  I think W3C WGs need to work with implementers to help
them understand where their approach is significantly affecting the
development of fully accessible (ie. internationalized) solutions.

It would be a shame if the MacOS people were simply unaware of the issue,
but happy to change it if advised.

RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/International/
http://rishida.net/blog/
http://rishida.net/

 
 

> -----Original Message-----
> From: Uma Umamaheswaran [mailto:umavs@ca.ibm.com] 
> Sent: 03 December 2007 21:15
> To: Marcos Caceres
> Cc: Arthur Barstow; Richard Ishida; public-appformats@w3.org; 
> public-i18n-core@w3.org; Thomas Roessler; 
> www-international@w3.org; www-international-request@w3.org
> Subject: Re: I18N issues for Widgets Spec [Was: Re: [Widgets] 
> ASCII File names - request for comments]
> 
> <Feedback from one of the PC experts in IBM - Ken Borgendale  
> -- kwb@us.ibm.com >
> 
> It seems to me that the problem here is that MacOS has a 
> non-conforming implementation of zip.  My first suggestion 
> would be to fix that problem.
> 
> On the other hand, there is a large amount of redundancy in 
> the UTF-8 encoding and if you only need to distinguish 
> between Cp437 and UTF-8 you could determine the encoding 
> correctly in almost all cases.  Any valid
> UTF-8 sequence which is not ASCII7 has at least two adjacent 
> byte >0x7F with the final one > 0xBF.  The simple rule would 
> be: if the string is valid UTF-8, process it as UTF-8, 
> otherwise as Cp437.
> ========
> 
> Best regards, Uma
> V.S. UMAmaheswaran, Ph.D.
> Globalization Centre of Competency, IBM Toronto Lab A2/SZ8, 
> 8200 Warden Avenue, Markham, ON, Canada, L6G1C7; +1 905 413 3474;
> Fax:905 413 4682; TieLine 313-3474; email: umavs@ca.ibm.com
> 
> 
Received on Tuesday, 4 December 2007 16:58:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:15 GMT