Hoi,<br>For the record; it is no longer allowed to make up language tags for Wikipedia.. There are some that are in existence from before the time when the language policy became in effect.<br>Tanks,<br> Gerard<br><br>
<div class="gmail_quote">2009/12/11 Doug Ewell <span dir="ltr"><<a href="mailto:doug@ewellic.org">doug@ewellic.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Michael(tm) Smith" <mike at w3 dot org> wrote:<br>
<br>
> So lacking any likelihood of those retired tags actually getting into<br>
> the IANA subtag registry, I'd suggest it'd at least be nice to have --<br>
> in whatever IETF or IANA document where it would be most<br>
> appropriate -- some statement of guidance to developers saying, "Tools<br>
> that check and report on instances of usage of language subtags SHOULD<br>
> use both the data in the IANA subtag registry and the available data<br>
> about IS0-639-3 retired codes."<br>
<br>
They should not. Code elements from ISO 639-3 that were retired prior<br>
to the approval of RFC 5646 were never valid in BCP 47 language tags.<br>
They may have been valid in non-BCP 47 applications that don't use the<br>
Registry, but instead use ISO 639 code elements directly (or make up<br>
their own, like the Wikipedias), but that is not at issue here.<br>
<font color="#888888"><br>
--<br>
Doug Ewell | Thornton, Colorado, USA | <a href="http://www.ewellic.org" target="_blank">http://www.ewellic.org</a><br>
RFC 5645, 4645, UTN #14 | ietf-languages @ <a href="http://is.gd/2kf0s" target="_blank">http://is.gd/2kf0s</a> <br>
<br>
_______________________________________________<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" target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br>
</font></blockquote></div><br>