<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi.<BR>
<BR>Doug Ewell doug at ewellic.org <BR>Mon Feb 1 01:00:30 CET 2010 <BR>
<BR>> Do not insert an Added field in the registration form. It is not called <BR>> for in Figure 5 of RFC 5646, which is found within Section 3.5. <BR>
<BR>Oops. (I went too many places looking for examples and still did not get that somehow.<BR>I had a ton of sleep last night so should not make more mistakes today hopefully.)<BR>
> You do need to have this field in the proposed record, though.<BR>
Yes, I see that.<BR>
> For subtags whose code elements are being retired from ISO 639-3, you <BR>> need a Deprecated field. You will also need a Preferred-Value field <BR>> (note capitalization), but only if there is *exactly one* subtag that is <BR>> preferred. . . . <BR>
This is know. <BR>
<BR>> btb' is different; any one of seven other subtags might be the <BR>> correct choice. A subtag cannot have more than one Preferred-Value, and <BR>> cannot have a so-called "multi-part" Preferred-Value; this is an <BR>> iron-clad rule. In this case, the information would have to be <BR>> expressed as a Comments field, such as:<BR>
> Comments: see beb, bum, bxp, eto, ewo, fan, mct<BR>
Thanks for refreshing me on this. (The case of Serbo-Croatian 'sh' now comes back.)<BR>
> . . .<BR>> But please hold off on Lushootseed for the moment.<BR>
I thought I was supposed to do all the first group of retired changes (I've already done 'lut', 'lushootseed', <BR>but have put in inside of brackets for now; let me know when you want it).<BR>
<BR>> For changes like these that track the core standards, whoever translates the ISO data <BR>> into BCP 47-compatible formats is the "author." In this case, that's <BR>> you.<BR>(O.k. thought I was doing minor clerical work here, following your directives.<BR>And anyway, I am finally getting shy, now that I got to do all this, but o.k.)<BR>
<BR>> Do not add Comments fields that simply duplicate the information in the <BR>> Preferred-Value field.<BR>
That was sort of what I suspected; sorry.<BR>
(It would have been almost easier for you to just copy and paste these than to train me would not it have?)<BR>
Best, <BR>
C. E. Whitehead<BR><A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A><BR><BR> </body>
</html>