<HTML>
<HEAD>
<TITLE>Re: Missing subtags 003 and 172</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
As far as I can tell, Mark is right here. Note that the 172 code was not created purely for statistical purposes,<BR>
but is an actual region (even if somewhat unstable). This is distinct from the codes 199, 432, 722, 778.<BR>
<BR>
This is a purely corrective action w.r.t. the rules in the RFC, and the question of whether these<BR>
codes are useful for language tagging is at this point irrelevant. For that matter, one may wonder<BR>
how the code 001 (World) is useful in language tagging...<BR>
<BR>
/Kent K<BR>
<BR>
<BR>
Den 2010-07-30 17.08, skrev "Mark Davis" <<a href="mark@macchiato.com">mark@macchiato.com</a>>:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE='font-size:11pt'><FONT FACE="Georgia, Times New Roman">We deliberately decided in the course of the BCP47 update to include all of the codes except for the following.<BR>
<BR>
</FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"> B. UN numeric codes for 'economic groupings' or 'other<BR>
groupings' MUST NOT be registered in the IANA registry and<BR>
MUST NOT be used to form language tags.<BR>
</FONT><FONT FACE="Georgia, Times New Roman">We made 830 optional, specifically because it is somewhat deprecated by the addition of the country codes for the islands instead. That is not the case for 003 and 172; these are as or more useful than other region codes. There are some other codes (like 062) that we can deprecate in CLDR, but not these.<BR>
<BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>