<div dir="ltr"><div class="gmail_default" style="font-family:"times new roman",serif">While that is an accurate response, it isn't the whole response. Even if ISO 639-1 were to add a two letter code:</div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif"><pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"> In order to avoid instability in the canonical form of tags, if a
two-character code is added to ISO 639-1 for a language for which a
three-character code was already included in either ISO 639-2 or ISO
639-3, the two-character code MUST NOT be registered. See
<a href="https://tools.ietf.org/html/bcp47#section-3.4">Section 3.4</a>.</pre></div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div><div class="gmail_default" style="font-family:"times new roman",serif">That means that such a 2 letter code would not be used by BCP47, which means it would effectively be pointless for language tagging. Most industry has shifted to using BCP47 as the source for codes for language, territory, etc, since they provide the stability that ISO doesn't.</div><div class="gmail_default" style="font-family:"times new roman",serif"><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font face="'times new roman', serif"><div style="background-color:transparent;margin-top:0px;margin-left:0px;margin-bottom:0px;margin-right:0px"><div></div></div><div style="background-color:transparent;margin-top:0px;margin-left:0px;margin-bottom:0px;margin-right:0px">Mark</div></font><div><div><font face="'times new roman', serif"><i><span style="font-style:normal"><i></i></span><i></i></i></font></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Feb 28, 2017 at 2:19 PM, Arthur Reutenauer <span dir="ltr"><<a href="mailto:arthur.reutenauer@normalesup.org" target="_blank">arthur.reutenauer@normalesup.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi Saroj,<br>
<br>
This discussion list is not responsible for the various ISO standard<br>
code sets; we only monitor the changes in ISO standards to reflect them<br>
in the language subtag registry (<a href="http://www.iana.org/assignments/language-subtag-registry" rel="noreferrer" target="_blank">http://www.iana.org/<wbr>assignments/language-subtag-<wbr>registry</a>).<br>
The institution responsible for maintaining ISO 639-1 is Infoterm<br>
(<a href="http://www.infoterm.info/standardization/iso_639_1_2002.php" rel="noreferrer" target="_blank">http://www.infoterm.info/<wbr>standardization/iso_639_1_<wbr>2002.php</a>), you can<br>
try and contact them but it is unlikely that they will consider new<br>
codes for adoption. I don’t know what the exact criteria are but it is<br>
very, very rare that codes are added to ISO 639-1. There are a few<br>
hints about what the criteria are on the website of the US Library of<br>
Congress that is the maintenance agency for ISO 639-2<br>
(<a href="http://www.loc.gov/standards/iso639-2/faq.html#13" rel="noreferrer" target="_blank">http://www.loc.gov/standards/<wbr>iso639-2/faq.html#13</a>).<br>
<br>
Best,<br>
<br>
Arthur<br>
______________________________<wbr>_________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" rel="noreferrer" target="_blank">http://www.alvestrand.no/<wbr>mailman/listinfo/ietf-<wbr>languages</a><br>
</blockquote></div><br></div>