I agree, except for the sentence:<br><br>> since the RFC already deprecates the use of most macrolanguages (including 'sh') in favor of encompassed language subtags.<br>
<br>Macrolanguages are <b>not</b> deprecated; only 'sh' is; that's why it is an anomaly. <pre class="newpage">%%<br>Type: language<br>Subtag: zh<br>Description: Chinese<br>Added: 2005-10-16<br>Scope: macrolanguage<br>
%%<br></pre> I think what you meant to say is that the RFC <i>favors</i> the use of encompassed languages over the use of their macrolanguages. <br><br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Mon, Jun 29, 2009 at 08:59, Phillips, Addison <span dir="ltr"><<a href="mailto:addison@amazon.com">addison@amazon.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think my opinion on what should happen would depend on the record Mark wants to register.<br>
<br>
One change that the new RFC makes to record 'sh' is that it will include the field "Macrolanguage". There is specific guidance about macrolanguage usage in the RFC, notably in section 4.1.1---where the encompassed languages of 'sh' appear in an example. It shouldn't, in theory, be necessary to deprecate 'sh', since the RFC already deprecates the use of most macrolanguages (including 'sh') in favor of encompassed language subtags.<br>
<br>
One problem with deprecating 'sh' is that we do not include a "Deprecated" field in the other macrolanguage subtag records. Presumably one would deprecate a macrolanguage if it were withdrawn or replaced with another code by ISO 639-3 or if the macrolanguage relationship were dissolved... that is, deprecation happens when something happens to the status of 'sh' as a macrolanguage or happens to other peer subtags.<br>
<br>
On the other hand, Mark has a point. Language tagging in the Balkans is freighted with enough different socio-political and historical nuances as it is. 'sh' and its encompassed languages serve mainly as an exception to the normal rules of tag meaning and stability. Although "macrolanguage-hood" is a different form of deprecation, I think preserving the current explicit deprecation of the subtag might benefit everyone more than strictly hewing to the RFC's apparent intentions.<br>
<br>
So right now I think I'd wait for Mark's request, since the nuances are likely to be what matters.<br>
<br>
Addison<br>
<br>
Addison Phillips<br>
Globalization Architect -- Lab126<br>
<br>
Internationalization is not a feature.<br>
It is an architecture.<br>
<div class="im"><br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:ietf-languages-bounces@alvestrand.no">ietf-languages-bounces@alvestrand.no</a> [mailto:<a href="mailto:ietf-languages-">ietf-languages-</a><br>
> <a href="mailto:bounces@alvestrand.no">bounces@alvestrand.no</a>] On Behalf Of Doug Ewell<br>
> Sent: Monday, June 29, 2009 6:05 AM<br>
> To: <a href="mailto:ietf-languages@iana.org">ietf-languages@iana.org</a><br>
</div><div class="im">> Subject: Re: Anomaly in upcoming registry<br>
><br>
</div><div><div></div><div class="h5">> Randy Presuhn <randy underscore presuhn at mindspring dot com><br>
> wrote:<br>
><br>
> >> ... It certainly isn't patently obvious to me that this is a bug<br>
> in<br>
> >> the draft-4645bis Registry that needs to be fixed.<br>
> ><br>
> > I think no one is suggesting that anything be done to draft-<br>
> 4645bis. I<br>
> > think re-opening 4645bis to make a change of this nature would be<br>
> > inappropriate.<br>
><br>
> No, I agree that Mark was not calling to change anything in<br>
> draft-4645bis, but rather in the "draft-4645bis Registry" -- the<br>
> Registry to be supplied to IANA by draft-4645bis, whose method of<br>
> construction is described in draft-4645bis.<br>
><br>
> My position is that the change Mark suggests may not be appropriate,<br>
> and<br>
> is certainly not a <span lang="en-US">slam dunk</span>. It depends<br>
> on<br>
> our interpretation of draft-4646bis and any priorities it does or<br>
> doesn't give to ISO 639-3 over other parts of ISO 639, and it<br>
> depends on<br>
> whether the relevant RA or JAC decides to correct the inconsistency<br>
> in<br>
> 639 by either (a) reviving "sh" in 639-1 and adding "hbs" to 639-2,<br>
> or<br>
> (b) withdrawing "hbs" from 639-3.<br>
><br>
> I don't see why the philosophical discussion necessarily must wait<br>
> until<br>
> the new Registry is in force, but if others want to wait, that's<br>
> fine<br>
> with me.<br>
><br>
> --<br>
> Doug Ewell * Thornton, Colorado, USA * RFC 4645 * UTN #14<br>
> <a href="http://www.ewellic.org" target="_blank">http://www.ewellic.org</a><br>
> <a href="http://www1.ietf.org/html.charters/ltru-charter.html" target="_blank">http://www1.ietf.org/html.charters/ltru-charter.html</a><br>
> <a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</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>
_______________________________________________<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>
</div></div></blockquote></div><br>