From: "Doug Ewell" Date: Wed, 15 Oct 2008 18:41:51 -0600 * From: "Doug Ewell" > CE Whitehead wrote: >> However, it is section 2.3 of the draft, "Modified Language Subtags," par. 3, that I was referring to: >> ". . . Language subtags corresponding to code elements that were identified in [ISO639-3] as representing collection codes, but not listed in [ISO639-5], were also assigned a Scope value of "collection". Doug, I see that ISO 639-3 is all macro-languages and individual languages (http://www.sil.org/ISO639-3/codes.asp); I guess then I just want an explanation of where language subtag elements are assigned a scope value of collection; I see no "collections" listed among the ISO 639-3 codes since 2.3 of the draft mentions this. >> I thought a note to this effect might be added to Section I, par. 2, to the end of the text below: >> "[draft-ietf-ltru-4646bis-17] expands on [RFC4646] by adding support for approximately 7,500 new primary and extended language subtags based on [ISO639-3] and [ISO639-5] alpha-3 code elements, and seven new region subtags based on [ISO3166-1] exceptionally reserved code elements. " >> If no one else agrees, I'll drop it, but I do think we could have this section a tiny bit more specific. Fine > I do not agree. The normative references to both ISO 639-3 and 639-5 state the full names of these standards, showing that 639-3 encodes individual languages while 639-5 encodes "language families and groups." Sections 2.2 and 2.3 already explain how 639-3 and 639-5 code elements are used to form language subtags. I don't see any need to elaborate on this in the Introduction. -- > Doug Ewell * Thornton, Colorado, USA * RFC 4645 * UTN #14 O.k. What is the exact meaning of the comments in section 2.3, par. 3? Because it is this that is confusing me actually, not the introduction. Thanks! (Sorry to ask such a dumb question) --C. E. Whitehead cewcathar at hotmail.com _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.