- From: Felix Sasaki <fsasaki@w3.org>
- Date: Mon, 11 Sep 2006 12:51:12 +0900
- To: ishida@w3.org
- Cc: www-i18n-comments@w3.org, public-i18n-core@w3.org, public-i18n-its@w3.org
Hello i18n core, This is a reply on behalf of the i18n ITS working group. See also http://www.w3.org/Bugs/Public/show_bug.cgi?id=3468 for our discussion. Thank you very much for your comment. We agreed to implement it. Please have a look at http://www.w3.org/International/its/itstagset/itstagset.html#language-information , especially the note after example 38. Please let us know within 2 weeks if you are satisfied. If we don't hear from you , we will assume this issue as closed. Regards, Felix Regards, Felixishida@w3.org wrote: > Comment from the i18n review of: > http://www.w3.org/TR/2006/WD-its-20060518/ > > Comment 41 > At http://www.w3.org/International/reviews/0606-its/ > Editorial/substantive: S > Owner: RI > > Location in reviewed document: > 5.1, 5.3.2 > > Comment: > We feel it is not acceptable that the markup proposed by ITS makes no mention of ways to define language for the content of ITS elements. At the very least, a proposed approach should be described in text, with xml:lang being held up as the most standard way to do things. Such text could say something like: > > > "xml:lang should be available on the span element, unless the format into which ITS is being integrated has an attribute that fulfills the role of xml:lang, in which case that attribute should be available on the span element." And similar for other elements defined for ITS. > > > ITS can point out that xml spec does define xml:lang in a global rules kind of way. > > > >
Received on Monday, 11 September 2006 03:51:32 UTC