<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br>Hi once more.<br><br><br><div>> From: doug@ewellic.org<br>> To: cewcathar@hotmail.com; ietf-languages@iana.org<br>> Subject: RE: Fourth batch of ISO 639-3 modifications<br>> Date: Fri, 30 Aug 2013 15:08:13 -0700<br>> <br>> CE Whitehead <cewcathar at hotmail dot com> wrote:<br>> <br>> > Doug, one more question: why is "Dhangu" retained as an additional<br>> > name for code element 'dhg'??<br>> > There is nothing in the ISO change file to say it should be retained<br>> > (see Change Request # 2012-047 in the .pdf file<br>> > http://www-01.sil.org/iso639-3/cr_files/639-3_ChangeRequests_2012_Sum&Add.pdf),<br>> > nor in the original change request:<br>> > http://www-01.sil.org/iso639-3/cr_files/2012-047.pdf<br>> <br>> That's correct. This is because, again, the data files are the normative<br>> source for ISO 639-3 data, not the change request forms (which may<br>> contain requests that are not accepted by the RA), and not the Summary<br>> of Outcomes PDF document (which may contain errors or omissions).<br>> <br>> The file iso-639-3.tab (formerly called iso-639-3_20130531.tab)<br>> contains:<br>> <br>> dhg I L Djangu <br>> <br>> which means "Djangu" is the reference name (for an Individual Living<br>> language). And the file iso-639-3_Name_Index.tab (formerly called<br>> iso-639-3_Name_Index_20130520.tab) contains:<br>> <br>> dhg Dhangu Dhangu<br>> dhg Djangu Djangu<br>> <br>> which means "Dhangu" is an alternate name.<br>Thanks. Sometime when my computer is not hanging up so much (or when I have a new one with more memory) I will look at these.<br>Sorry I could not be of more help.<br>> <br>> I am beginning to think it was a mistake to include a link to the<br>> original change request in each registration form, since it seems to be<br>> giving the impression that the change requests are authoritative in some<br>> way. They are input to the RA's process, but not to ours. They are<br>> interesting as background material on the language(s) involved. Next<br>> year I will try to make the roles of the various documents more clear.<br>> <br>I think the change request link is helpful, though it can cause confusion. And I think that you've made the role of the various documents clear on the list by this point (perhaps someday an update to RFC 5646 section 3.5 or perhaps a note a langtag.net "How to Register a New Subtag" might be in order; but I think I am the only one on the list who has expressed confusion).<br>> > (Sorry to ask another such question; since I am still unsure where the<br>> > data files are, maybe they differ again from the .pdf)<br>> <br>> http://www-01.sil.org/iso639-3/download.asp<br>> <br>> > (I still may look over the fourth, fifth, and sixth batches of subtag<br>> > modifications a bit more but have been through most everything now;<br>> > which is a good feeling, as just reading through these is tedious. )<br>> <br>> Imagine preparing them.<br>That must have taken some time.<br>Best,<br><br>--C. E. Whitehead<br>cewcathar@hotmail.com<br><br>> <br>> --<br>> Doug Ewell | Thornton, CO, USA<br>> http://ewellic.org | @DougEwell <br>> <br></div> </div></body>
</html>