<meta charset="utf-8"><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; color: rgb(51, 51, 51); ">The grandfathered tags behave differently than anything else. All the other tags are productive: you can combine them in different ways with expected results, while the grandfathered tags are atomic; you can't combine one of them with, say, a region. Moreover, you can write APIs to deal with that structure, returning the base language code, script code, etc. The uniformity of program APIs is of extreme importance when you are dealing with massive amounts of program code.<div>
<br></div><div><div>Of course we could parse en-GB-oed. But it doesn't fit into the regular ABNF production rules, and so doesn't work well in APIs.</div><div><br>Out of the billions of possible language tags (without even counting combinations using variants), there are <i>literally</i> only a handful of grandfathered codes (that cannot be correctly mapped to regular language tags). If we can fix these few, then there is nothing standing in the way of everyone being able to use all of them effectively.</div>
<div><br></div><div>That is, for existing data, we (and others like us) would convert tags like en-GB-oed on input to regular tags; then the information is still accessible. Otherwise our only choices are to dump the data or map to the 'closest' code.</div>
<div></div></div></span><div><br></div>Mark<br>
<br><br><div class="gmail_quote">On Wed, Jan 20, 2010 at 10:23, Michael Everson <span dir="ltr"><<a href="mailto:everson@evertype.com">everson@evertype.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 20 Jan 2010, at 01:58, Mark Davis ☕ wrote:<br>
<br>
</div><div class="im">> Why do this? Well, at Google we convert anything that has an<br>
> irregular format to a regular format.<br>
<br>
</div><div class="im">Which means what? Your programmers aren't able to identify and parse<br>
the string "en-GB-oed"? Guess what, Mark... that has been in use since<br>
2003. There's data out there in it.<br>
<br>
Please explain what it is that you are up to.<br>
<br>
Michael Everson * <a href="http://www.evertype.com/" target="_blank">http://www.evertype.com/</a><br>
<br>
</div>_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br>
<div><div></div><div class="h5"><a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br>
</div></div></blockquote></div><br>