<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi, Addison, all.<BR><BR>Didn't we finally agree to hold off acting on 'erzgeb' until 'sxu' was listed in the subtag registry--that is aren't we waiting on the publication of the updated RFC 4646 to act on that variant request too?<BR>
(see: <A href="http://www.alvestrand.no/pipermail/ietf-languages/2008-March/007674.html">http://www.alvestrand.no/pipermail/ietf-languages/2008-March/007674.html</A><BR>
"Unfortunately, that means the request must wait for formal<BR>approval until after the next revision of BCP 47, as we do not yet<BR>actually support ISO 639-3 code elements as language subtags.<BR>Informally, though, there's no reason why you shouldn't start using<BR>sxu-erzgeb right away."<BR>
Also see:<BR>
<A href="http://www.alvestrand.no/pipermail/ietf-languages/2008-March/007669.html">http://www.alvestrand.no/pipermail/ietf-languages/2008-March/007669.html</A>)<BR><BR>
<BR>
Correct me if I'm wrong but I do not remember finally registering 'erzgeb' as a variant. So just as for Aluku, Ndyuka, and Pamaka, registration of 'erzgeb' is still to be discussed down the road, upon the publication of the updated rfc 4646 draft?<BR>
<BR>
(However, Addison is right; we did briefly consider registering 'erzgeb' as a variant of 'de' or of 'gem' before deciding to wait)<BR>
<BR>
Thanks.<BR>
<BR>
--C. E. Whitehead <BR>
<A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A> <BR><BR><BR><BR>
<HR id=stopSpelling>
<P><BR>
From: addison@amazon.com<BR>To: cewcathar@hotmail.com; ietf-languages@iana.org<BR>Date: Tue, 27 Jan 2009 19:15:22 -0800<BR>Subject: RE: Suggestion: registration of variant subtags for Aluku, Ndyuka, and Pamaka (Suriname/French Guiana English-based Creoles)<BR><BR><BR>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass p
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass pre
{margin-bottom:.0001pt;font-size:10.0pt;font-family:'Courier New';}
.ExternalClass span.EC_HTMLPreformattedChar
{font-family:Consolas;}
.ExternalClass span.EC_EmailStyle20
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .EC_MsoChpDefault
{font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.EC_Section1
{page:Section1;}
</STYLE>
<DIV class=EC_Section1>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"> <BR>(I assume M. Lang wants NM because MN is taken but I think we only register region codes when a UN M.49 code becomes available with no ISO 3166 code??? or else when a 3166-1 code is created with no corresponding UN M.49 code??? Both seem like odd situations??? Someone please clarify this discussion for me; I thought we only registered variants, but it seems that the language subtag reviewer can also, in some unusual circumstances, register region codes??)</SPAN><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"></SPAN></P>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">We register only ISO 3166-1 and UN M.49 codes as region subtags. If and when the designation/official organization/name for a country changes, both standards usually react fairly quickly. There is no point in trying to anticipate them.</SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'"><BR> <BR>Back to the variants: I'm fine with waiting till till RFC 4646 is published before considering M. Vaillant's variants; (Sorry; I thought that discussion </SPAN><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"></SPAN></P>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Recte: 4646bis.</SPAN></P>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Verdana','sans-serif'">was o.k. since we had discussed "erzgeb" while waiting for a successor of RFC 4646 ; see <A href="http://www.alvestrand.no/pipermail/ietf-languages/2008-March/007672.html">http://www.alvestrand.no/pipermail/ietf-languages/2008-March/007672.html</A> but of course, there will -- hopefully-- not be that long a wait for RFC 4646 & it makes sense to wait!)</SPAN><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Verdana','sans-serif'"></SPAN></P>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Please note: ‘erzgeb’ modified an *<B>existing</B>* language subtag. These proposals modify subtags that themselves cannot be registered until 4646bis is official.</SPAN></P><PRE><SPAN style="COLOR: #1f497d">Addison</SPAN></PRE><PRE><SPAN style="COLOR: #1f497d"> </SPAN></PRE>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 9pt; COLOR: #1f497d; FONT-FAMILY: 'Lucida Sans Unicode','sans-serif'">Addison Phillips</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 9pt; COLOR: #1f497d; FONT-FAMILY: 'Lucida Sans Unicode','sans-serif'">Globalization Architect -- Lab126</SPAN><SPAN style="FONT-SIZE: 9pt; COLOR: #1f497d; FONT-FAMILY: 'Lucida Sans Unicode','sans-serif'"></SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 9pt; COLOR: #1f497d; FONT-FAMILY: 'Lucida Sans Unicode','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 9pt; COLOR: #1f497d; FONT-FAMILY: 'Lucida Sans Unicode','sans-serif'">Internationalization is not a feature.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 9pt; COLOR: #1f497d; FONT-FAMILY: 'Lucida Sans Unicode','sans-serif'">It is an architecture.</SPAN></P></DIV>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P><PRE> </PRE></DIV></body>
</html>