<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<pre><font style="" face="Arial">Hi.</font><br></pre>
Doug Ewell
<a href="mailto:ietf-languages%40alvestrand.no?Subject=Re%3A%20Nepali%20Extension%20Language%20Question%20%28WAS%3A%20Review%20period%3B%0A%20Nepali%20and%20Oriya%29&In-Reply-To=%3C6E6B5FABD823472595BB1DB496B38AFC%40DougEwell%3E" title="Nepali Extension Language Question (WAS: Review period; Nepali and Oriya)">doug at ewellic.org
</a><br>
Wed Aug 8 02:11:49 CEST 2012
<hr>
<pre>> CE Whitehead <cewcathar at hotmail dot com> wrote:
>>><i> Perhaps in the future, I should add the Change Request number to each
</i>>>><i> registration form, so reviewers can more easily find these pages.
</i>>><i>
</i>>><i> (More work for you? Let me know if you want me to do this in the
</i>>><i> future. Thanks.
</i>>><i> Maybe I should do it for these recently approved changes sometime this
</i>>><i> week. I can at least do that.)
</i>
> It shouldn't be necessary for any of them. All ISO 639-3 info for a
> given code element can be found by visiting:
<a href="http://www.sil.org/iso639-3/documentation.asp?id=xxx">> http://www.sil.org/iso639-3/documentation.asp?id=xxx</a><br><br>> substituting the actual 3-letter code element for the 'xxx'. This works
> even with ISO 639-2 and 639-5 collection code elements, though not with
> 2-letter ISO 639-1 code elements. <br><br><font style="" face="Arial">Yes, this works; for [ori] ("Oriya") see: http://www.sil.org/iso639-3/documentation.asp?id=ori you just have to scroll down the page for a link to the change request!</font><font style="" face="Arial"><br></font><font style="" face="Arial">(I also found these change requests by going to the 2011 code changes and clicking on the link for "more":</font><font style="" face="Arial"><br></font><font style="" face="Arial"> http://www.sil.org/iso639-3/chg_requests.asp?order=CR_Number&chg_status=2011 -- but note here that some of these change requests were rejected</font><font style="" face="Arial"><br></font><font style="" face="Arial">and so there will be no code change processed in such cases; as for the order here, I assume it is in the order the change requests were made.)</font><font style="" face="Arial"><br></font><br>> In most cases, the RA's page contains
> a link to an Ethnologue page with even more information about the
> language (though of course it is not the only source).
>><i> I note that the change request [for Oriya] indicated much more shared
</i>>><i> vocabulary between Sambalpuri and the rest of the Oriyan language than
</i>>><i> was noted between Dotyali and Nepali, but finally the request said
</i>>><i> (rather flatly) that this was so because both were related albeit via
</i>>><i> Sanskrit.
</i>>><i> So I don't know in this case what to do.
</i>
> In that case, I recommend you do nothing. <br><font style="" face="Arial">Thanks. I would not do anything; it would be subject to the reviewer to add the extlang for these if it were decided that doing so was appropriate.</font><font style="" face="Arial"><br></font>> If anyone here does have
> knowledge of the Nepali or Oriya situation, they should speak up.
> Otherwise, we will not add the extlangs.
<font style="" face="Arial">Thanks for the info.</font><font style="" face="Arial"><br></font><font style="" face="Arial">Sincerely,</font><font style="" face="Arial"><br></font><font style="" face="Arial"><br></font><font style="" face="Arial">--C. E. Whitehead</font><font style="" face="Arial"><br></font><font style="" face="Arial">cewcathar@hotmail.com</font> <br> > --
> Doug Ewell | Thornton, Colorado, USA
<a href="http://www.ewellic.org/">> http://www.ewellic.org</a> | @DougEwell
</pre> </div></body>
</html>