- From: Robin Berjon <robin@berjon.com>
- Date: Wed, 2 Sep 2009 23:37:02 +0200
- To: ishida@w3.org
- Cc: public-Webapps@w3.org, public-i18n-core@w3.org
Hi, On Jul 9, 2009, at 21:15 , ishida@w3.org wrote: > We second Martin's comments at > http://lists.w3.org/Archives/Public/public-i18n-core/2009AprJun/0067.html > . So do we, and we've therefore attempted to address them. > The term URI appears to mean URI and *not* IRI universally here. That was not the intention. Hopefully it is clearer now. > No non-ASCII paths are given in examples and the relationship to IRI > is not specified. I've changed them to use non-ASCII paths. > The Packaging and Configuration spec mentions encodings and permits > the full range of Unicode in file names, so the lack of specificity > is at least an oversight. I suspect that, depending on the use of > the URI, they really do mean IRI here, though. Packaging and > Configuration strongly suggests the use of the UTF-8 encoding for > Zip relative paths and human-readable (native encoded) URIs would be > more in keeping with the usability desires of web-apps. That is entirely correct, hopefully it's better now. Thanks! -- Robin Berjon - http://berjon.com/
Received on Wednesday, 2 September 2009 21:37:39 UTC