Kent Karlsson <kent dot karlsson14 at comhem dot se> wrote:
1) File production issue: There is some garbage text at the end of http://www.ewellic.org/lstreg-4646bis-draft-06.txt.
These two lines are added by my Web hosting provider, GoDaddy, as part of the mechanism they use to add banner ads to my HTML pages. They are, of course, useless for text files, but if I ask GoDaddy to fix the problem, they will probably tell me to upgrade from free hosting to paid hosting.
I'll add zipped files, which I don't think will be adulterated, and a disclaimer about the garbage at the end of the unzipped files.
2) Not an LTRU issue, but 639-2 has the approach of having the word "languages" (or "other") in the descriptions for collection codes. However, the following two collection codes do not have the word "languages" (nor "other") in their descriptions: Subtag:bh Description:Bihari Added:2005-10-16 Scope:collection Subtag:him Description:Himachali Added:2005-10-16 Scope:collection
As you said, this isn't an LTRU issue; we use the exact ISO 639 names, and document where we don't. I checked, and both 639-2 and 639-3 call these "Bihari" and "Himachali". I wonder if this is one reason why 639-5 missed them.
-- Doug Ewell * Arvada, Colorado, USA * RFC 4645 * UTN #14 http://www.ewellic.org http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ _______________________________________________ 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.