<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="&#1;" xmlns="http://www.w3.org/TR/REC-html40">

<head>

<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* 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
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
 /* List Definitions */
 @list l0
        {mso-list-id:1798641387;
        mso-list-template-ids:-794128286;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</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-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It is *<b>not</b>* possible to change the ID of an already-encoded
category, so requesting such a change is definitely not worth pursuing.
Changing the name without changing the semantic is possible, however, and
changes to a semantic are possible with restrictions so as to avoid causing
existing usage to become invalid.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Peter<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ietf-languages-bounces@alvestrand.no
[mailto:ietf-languages-bounces@alvestrand.no] <b>On Behalf Of </b>CE Whitehead<br>
<b>Sent:</b> Friday, January 23, 2009 2:59 PM<br>
<b>To:</b> ietf-languages@iana.org<br>
<b>Subject:</b> RE: Suggestion: registration of variant subtags for Aluku,
Ndyuka, and Pamaka (Suriname/French Guiana English-based Creoles)<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Hi.&nbsp;
<br>
&nbsp;<br>
M. Vaillant:<br>
<br>
As far as I understand, it is&nbsp;possible to change the ISO639-3 codes and
language names (Joan Span's&nbsp;posting has just reminded me of this), but you
are right; I do not think&nbsp;a change to the code itself&nbsp;would be worth
pursuing; if you wished to add additional names however, that would be fine:<br>
<br>
<a href="http://www.sil.org/iso639-3/submit_changes.asp#Types">http://www.sil.org/iso639-3/submit_changes.asp#Types</a><br>
&quot;<br>
The types of changes that are possible are to:<o:p></o:p></span></p>

<ol start=1 type=1>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>modify
     the reference information for an existing code element (reference name and
     additional names, language type. language scope or relationship to a <a
     href="http://www.sil.org/iso639-3/macrolanguages.asp">macrolanguage</a>
     grouping). <o:p></o:p></span></li>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>retire
     a code element from use, including merging its scope of denotation into
     that of another code. <o:p></o:p></span></li>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>split
     an existing code element into two or more separate language code elements.
     <o:p></o:p></span></li>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>create
     a new code element for a previously unidentified language. <o:p></o:p></span></li>
</ol>

<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>&quot;<br>
&nbsp;<br>
<a href="http://www.sil.org/iso639-3/submit_changes.asp#Submitting">http://www.sil.org/iso639-3/submit_changes.asp#Submitting</a><br>
&nbsp;<br>
And we can still approve the variant subtags&nbsp;(once&nbsp;RFC 4646 is
published?&nbsp; Is that the consensus?)<br>
&nbsp;<br>
Thanks.&nbsp;<br>
&nbsp;<br>
--C. E. Whitehead<br>
<a href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</a> <br>
<br>
<br>
<br>
&gt; From: pascal.vaillant@guyane.univ-ag.fr<br>
&gt; To: cewcathar@hotmail.com; ietf-languages@iana.org<br>
&gt; Subject: Re: Suggestion: registration of variant subtags for Aluku,
Ndyuka, and Pamaka (Suriname/French Guiana English-based Creoles)<br>
&gt; Date: Fri, 23 Jan 2009 15:06:48 -0300<br>
&gt; <br>
&gt; <br>
&gt; Le Friday 23 January 2009, vous avez écrit :<br>
&gt; &gt; Hi, the information at Wikipedia &amp; Ethnologue suggests that M.
Vaillant is<br>
&gt; &gt; correct; these seem to be three dialects.<br>
&gt; &gt;<br>
&gt; &gt; But I am not familiar with these either.<br>
&gt; &gt;<br>
&gt; <br>
&gt; Actually my request reflects the view of a group of specialists<br>
&gt; in my research lab, CELIA, which is specialized in the field<br>
&gt; (http://celia.cnrs.fr). Two of them wrote one of the bibliographical<br>
&gt; references cited. The Ethnologue catalogue edited by the SIL <br>
&gt; (http://www.ethnologue.com/show_language.asp?code=djk),<br>
&gt; which is the ground on which the ISO 639-3 standard is based,<br>
&gt; also considers the three varieties as dialects of a same language,<br>
&gt; not as languages of a same macro-language. The disagreement between<br>
&gt; specialists would rather lie in one detail, namely the mnemonic<br>
&gt; chosen to name that language : 'djk' (language tag chosen by<br>
&gt; the SIL) is a reminder of Djuka, which is but one variety of<br>
&gt; the language (though the most numerous). But this is not a matter<br>
&gt; to be discussed here, I suppose.<br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Pascal Vaillant<br>
&gt; <br>
&gt; <o:p></o:p></span></p>

</div>

</body>

</html>