<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi. I would like to see a comment in this case too.<br><br>Best,<br><br>C. E. Whitehead<br>cewcathar@hotmail.com<br><br>Doug Ewell
<a href="mailto:ietf-languages%40alvestrand.no?Subject=Deprecation%20of%20heploc%20subtag%20%28refiling%20with%20corrected%20spelling%29&In-Reply-To=" title="Deprecation of heploc subtag (refiling with corrected spelling)">doug at ewellic.org
</a><br>Sun Dec 20 19:36:15 CET 2009
<!--beginarticle-->
<pre>> Randy Presuhn <randy underscore presuhn at mindspring dot com> wrote:<br><br>>>><i> Preferred-Value: alalc97<br></i>>><i><br></i>>><i> I hope no one understands this as meaning that a tag<br></i>>><i> of ja-Latn-hepburn-heploc should be replaced by one<br></i>>><i> of ja-Latn-hepburn-alalc97. Presumably the intent was<br></i>>><i> ja-Latn-alalc97, but I don't see how one would figure<br></i>>><i> that out from the registry contents alone.<br></i><br>> Perhaps <sigh /> we need a comment.<br><br>>><i> I think the lesson from this is that Preferred-Value doesn't<br></i>>><i> quite work in some cases, e.g., when the new preferred-value<br></i>>><i> is "generic" (lacks a prefix) and the variant to which is<br></i>>><i> is added has a prefix with multiple subtags.<br></i><br>> I don't think we anticipated replacing a second-level variant with a <br>> first-level variant. I know I didn't anticipate that we would deprecate <br>> a just-approved variant in favor of another so quickly, hastening the <br>> day when we would face this problem.<br><br></pre><br> </body>
</html>