<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Mongolian Baiti";
panose-1:3 0 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Segoe UI Symbol";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">The mail from Doug confirming that the subtag registry had been updated didn’t land in my inbox,
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:.5in">IANA has updated the language subtag registry. See the “abl1943,”
<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in">“ao1990,” and “colb1945” variant entries at<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a><o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><a href="http://www.iana.org/assignments/lang-subtags-templates">http://www.iana.org/assignments/lang-subtags-templates</a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I had therefore incorrectly inferred that the correction to the spelling of Portuguese in the one record would extend the review period. Happily that is not the
case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Thank you everyone who contributed to the discussion that led to the addition of these subtags!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Ietf-languages [mailto:ietf-languages-bounces@alvestrand.no]
<b>On Behalf Of </b>Doug Ewell<br>
<b>Sent:</b> Friday, May 15, 2015 10:57 AM<br>
<b>To:</b> Michael Everson; ietflang IETF Languages Discussion<br>
<b>Subject:</b> RE: Second correction to 'ao1990' : Prefix field - widening to 'pt'<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">I'm really confused now. The Portuguese subtags were registered a few days ago.<br>
<br>
I understand that Andrew would prefer that the tags be registered first, with less-than-ideal prefixes, and then go back and reopen the debate over the Prefix field. That is actually the opposite of what I said, though it is a valid point.<br>
<br>
I guess my objection is to calling these changes "corrections" when they were at the heart of the lengthy debate we had, and the Prefix fields that were finally registered were explicitly the ones Michael wanted.<br>
<br>
--<br>
Doug Ewell | <a href="http://ewellic.org">http://ewellic.org</a> | Thornton, CO </span>
<span style="font-size:11.0pt;font-family:"Segoe UI Symbol",sans-serif">🇺🇸</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:everson@evertype.com">Michael Everson</a></span><br>
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sent: </span></b><span lang="AR-SA" style="font-size:11.0pt"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">5/</span><span lang="AR-SA" style="font-size:11.0pt"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">15/</span><span lang="AR-SA" style="font-size:11.0pt"></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">2015
11:17</span><br>
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">To: </span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:ietf-languages@iana.org">ietflang IETF Languages Discussion</a></span><br>
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Subject: </span>
</b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Re: Second correction to 'ao1990' : Prefix field - widening to 'pt'</span><o:p></o:p></p>
</div>
<p class="MsoNormal">On 15 May 2015, at 18:10, Andrew Glass (WINDOWS) <<a href="mailto:Andrew.Glass@microsoft.com">Andrew.Glass@microsoft.com</a>> wrote:<br>
<br>
> I would have preferred "Prefix: pt", however, for my purposes, I can live with the current solution. Getting the tag registered in a timely way is a higher priority for me at this point than the precise form of the prefix. Therefore, I'd prefer to follow
Doug's suggestion and allow the registration to proceed as is before opening up the debate over the prefix once more.<br>
<br>
I concur. <br>
<br>
Michael Everson * <a href="http://www.evertype.com/">http://www.evertype.com/</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">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><o:p></o:p></p>
</div>
</body>
</html>