<div dir="ltr">There is no structure in 4646 or 4646bis for deprecating a prefix X for a subtag Y. However, the same effect would be achieved by just deprecating X, so I don't think we need such structure.<br><br clear="all">
Mark<br>
<br><br><div class="gmail_quote">On Mon, Aug 4, 2008 at 3:57 PM, Broome, Karen <span dir="ltr"><<a href="mailto:Karen_Broome@spe.sony.com">Karen_Broome@spe.sony.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;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Hmm. But deprecation occurs on the entire record. Is there a way
to indicate that a single prefix is deprecated but not the tag? If we can add
prefixes later, we ought to be able to deprecate them too. But I'm not sure how
we'd do this in the current structure.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Karen</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<div style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0in 0in 0in 4pt;">
<div>
<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;">
<a href="mailto:ietf-languages-bounces@alvestrand.no" target="_blank">ietf-languages-bounces@alvestrand.no</a>
[mailto:<a href="mailto:ietf-languages-bounces@alvestrand.no" target="_blank">ietf-languages-bounces@alvestrand.no</a>] <b>On Behalf Of </b>Mark Davis<br>
<b>Sent:</b> Monday, August 04, 2008 3:53 PM<br>
<b>To:</b> Frank Ellermann<div class="Ih2E3d"><br>
<b>Cc:</b> <a href="mailto:ietf-languages@alvestrand.no" target="_blank">ietf-languages@alvestrand.no</a><br>
</div><div class="Ih2E3d"><b>Subject:</b> Re: LANGUAGE SUBTAG REGISTRATION FORM: pinyin</div></span></p>
</div>
</div>
<p> </p>
<div>
<p style="margin-bottom: 12pt;">No. According to the RFC, we
can add other prefixes later.<br>
<br clear="all">
Mark<br>
<br>
</p><div><div></div><div class="Wj3C7c">
<div>
<p>On Mon, Aug 4, 2008 at 12:21 PM, Frank Ellermann <<a href="mailto:nobody@xyzzy.claranet.de" target="_blank">nobody@xyzzy.claranet.de</a>> wrote:</p>
<div>
<p style="margin-bottom: 12pt;">Randy Presuhn wrote:<br>
<br>
> "why didn't they use '-pinyin'?"</p>
</div>
<p>Just a theoretical thought, if we take -pinyin with prefix<br>
zh-Latn- now there's no way to get rid of the prefix later.<br>
<br>
So if folks later want "pinyin" with prefix cmn-Latn- and<br>
others, but without zh-Latn-, they'd be forced to invent<br>
a new variant, say -pinyin2, and that would allow them to<br>
deprecate -pinyin in favour of -pinyin2.<br>
<br>
If that is exactly what you want (later, when cmn exists),<br>
you could use -pinyin1 now, and deprecate it in favour of<br>
the later "real" -pinyin with the "real" prefix cmn-Latn-<br>
instead of the slightly "unreal" zh-Latn-pinyin1 possible<br>
today.<br>
<span style="color: rgb(136, 136, 136);"><br>
Frank</span></p>
<div>
<div>
<p><br>
_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no" target="_blank">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></p>
</div>
</div>
</div>
<p> </p>
</div></div></div>
</div>
</div>
</div>
</blockquote></div><br></div>