Den 2009-02-21 03.37, skrev "Doug Ewell" <doug at ewellic.org>:
> Kent Karlsson <kent dot karlsson14 at comhem dot se> wrote:
>
>> I agree, but I also note that there are some changes noted in
>> http://www.loc.gov/standards/iso639-5/changes.php. Many of them refer
>> only to the French name(s), which aren't picked up for LSR, but there
>> are a few others that should be picked up. I see at least one, namely
>> the English name change for ngf.
>
> Kent raises an excellent point. Fortunately, your editor is on top of
> it. The changes from the original PDF chart are as follows:
>
> 1. 'car' for "Carib languages" has been deleted. This is consistent
> with the discussion I had with Rebecca Guenther and Joan Spanne,
> captured in the next-to-last paragraph of Section 2.3 in draft-4645bis.
> (Now that the decision is reflected in the standard, it'll be nice to
> get rid of that shady-sounding passage.)
>
> 2. 'day' for "Land Dayak languages" has been added. Since it was
Side remark: I have seen translations of this one as just "Dayak".
But the Land Dayak languages appears to be a subset of the Dayak
languages. At least according to Wikipedia:
http://en.wikipedia.org/wiki/Dayak_languages,
http://en.wikipedia.org/wiki/Bidayuh.
(In addition there is the retired code dyk for Land Dayak [languages]...)
> already in 639-2, it's already in draft-4645bis and marked as a
> collection. There are still two other collections, Bihari and
> Himachali, which are not in 639-5.
I think this holds also for "chs", Chumash, which I gather is the code
that is referred to in "1 retirement of a code element representing a
language family whose constituents were already present in [the] code set.
This code element will be recommended for inclusion in ISO 639-5". See
http://www.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2008_Sum&add.pdf.
(But at the moment chs is not covered by any part of 639, except as
"retired"...)
/kent k
> 3. As Kent observed, 'ngf' has been renamed from "Trans New Guinea" to
> "Trans-New Guinea languages". This needs to be fixed in
> draft-4645bis-10.
>
> As a side note, in case anyone else spots this with a diff program, the
> ISO 639-5 file spells the names "Creoles and pidgins, English-based" and
> "Creoles and pidgins, French-based" with U+2011 NON-BREAKING HYPHEN.
> They didn't do this for "Creoles and pidgins, Portuguese-based", nor for
> any other name that involves a hyphen. As co-designated expert for RFC
> 4646 and the Language Subtag Reviewer's clerical assistant, I intend to
> convert these to ASCII hyphens in draft-4645bis, as described in
> draft-4646bis, Section 3.1.5, paragraph 9. (If anyone objects that I'm
> not the Reviewer, I can always ask him.)
>
>> Maybe there are other differences not noted on the changes page.
>
> I think I've got them all, but additional reviewing eyes are always
> welcome.
>
>> Especially since our current 639-5 data was picked up from an
>> internal(?) draft document.
>
> It was actually taken from an official PDF copy of the final approved
> standard, obtained through less-than-official channels.
>
> --
> Doug Ewell * Thornton, 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 ?
>
>
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.