- From: Addison Phillips <addison@yahoo-inc.com>
- Date: Thu, 21 Sep 2006 21:02:52 -0700
- To: fsasaki@w3.org
- CC: www-i18n-comments@w3.org, public-i18n-core@w3.org, public-i18n-its@w3.org
That's fine with me. It just looked really weird to reference 4646 up above in your text and then the familiar "3066 or successor" rubric later (without mentioning the connection). Addison Felix Sasaki wrote: > Hi Addison, all, > > We discussed this at the thread at > http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0136.html > and came up with the following wording: > > "Applying the Language Information data category to xml:lang attributes > using global rules is not necessary, since xml:lang is the standard way to > specify language information in XML. xml:lang is defined > in terms of RFC3066 or its successor. (RFC4646 is the successor to RFC > 3066.)" > We would have a normative reference to RFC4646 and a non-normative one to > RFC3066. > > Would that be fine with you? > > Felix > >> Really I think you ought to use the latest reference. RFC 4646 is >> published and can be referenced. Pointing to the older, obsolete, RFC >> may confuse people needlessly. Your current text says: >> >> -- >> Applying the Language Information data category to xml:lang attributes >> using global rules is not necessary, since xml:lang is already defined >> in terms of RFC3066 or its successor. >> -- >> >> It might be better to append a note to that sentence: >> >> -- >> Applying the Language Information data category to xml:lang attributes >> using global rules is not necessary, since xml:lang is already defined >> in terms of RFC3066 or its successor. (RFC4646 is the successor to RFC >> 3066.) >> -- >> >> Best Regards, >> >> Addison >> >> Yves Savourel wrote: >>> Hi Richard, >>> >>> The reference has been changed to 'RFC3066 or its successor' with a link >>> to a reference to the "Language Identification" section of >>> the XML specification. >>> See >>> http://www.w3.org/International/its/itstagset/itstagset.html#langinfo-definition >>> >>> 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. >>> >>> Cheers, >>> -yves >>> >>> >>> -----Original Message----- >>> From: public-i18n-its-request@w3.org >>> [mailto:public-i18n-its-request@w3.org] On Behalf Of Richard Ishida >>> Sent: Monday, September 11, 2006 1:09 PM >>> To: 'Felix Sasaki' >>> Cc: www-i18n-comments@w3.org; public-i18n-core@w3.org; >>> public-i18n-its@w3.org >>> Subject: RE: [Comment on ITS WD] xml:lang = language info, please >>> >>> >>> Personal comment: >>> >>> "Applying the language information data category to xml:lang attributes >>> using global rules is not necessary, since xml:lang is >>> already defined in terms of [RFC 4646]." >>> >>> Strictly speaking xml is defined in terms of RFC 3066 or its successor. >>> It may be better to say "in terms of [BCP 47]" at this >>> location. If not, you should add, or it's successor. (Bear in mind >>> that RFC 4646bis is just around the corner, relatively >>> speaking.) >>> >>> RI >>> >>> >> -- >> Addison Phillips >> Globalization Architect -- Yahoo! Inc. >> >> Internationalization is an architecture. >> It is not a feature. >> >> > > -- Addison Phillips Globalization Architect -- Yahoo! Inc. Internationalization is an architecture. It is not a feature.
Received on Friday, 22 September 2006 04:03:15 UTC