- From: Yves Savourel <ysavourel@translate.com>
- Date: Thu, 16 Apr 2009 21:37:27 -0600
- To: <marcosc@opera.com>
- CC: "'public-webapps'" <public-webapps@w3.org>, <public-i18n-core@w3.org>
Hi Marcos, A few notes: === From a localizer viewpoint (so maybe not from a user-agent efficiency view), using the locale folders method is likely better than the localized elements method: Having a document with the same content in multiple languages often requires much more manipulations to get translated in several languages, and possibly some manual work (e.g. to put back all the translations in the same document) than monolingual files. While this seems not a big deal, it is actually quite time consuming when you are starting to have updates See the best practice #12 listed in "Best Practices for XML Internationalization" [1] for more detailed reasons. [1] http://www.w3.org/TR/xml-i18n-bp/#DevMLDoc So, while I see that it is a valid and even useful method, it is also one that has more side effects than the locale folders one. === In section 8 there is: "Localized config.xml - The author has declared at least one xml:lang attribute for an element in the configuration document." It sounds like the author could have declared more than one xml:lang attribute for a single element. Did you mean something like: "For each given type of element in the configuration document the author has at least one with the xml:lang attribute"? Cheers, -ys
Received on Friday, 17 April 2009 03:38:13 UTC