<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<BR>Hi, Peter, <BR>
<BR>
thanks for your history of the Chinese case.<BR>
<BR>
However, what confuses me is why are some languages made extension languages?<BR>
<BR>
It makes sense to me to make a language an extension language of a macrolanguage if all the extension languages under that macrolanguage are generally written more or less identically (as is the case for the Chinese languages written in Chinese script; similarly in Arabic, standard Arabic is the only written form). Then it would make sense to allow users to tag these languages using both the macro-language code and the extension-language code--<BR>
wherease if the languages appear different in writing, I don't see any reason to tag them with anything but their own unique code, ever.<BR>
<BR>
I don't know if this idea is off-base or not. If my idea is not off-base, then I would not think that either the Latvian/Latgalian pair or the Lithuainian/Samogithian pair would need to be registered as extension languages once the new codes are in place (assuming these codes will be approved).<BR>
<BR>
Best,<BR>
<BR>
C. E. Whitehead<BR>
<A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A><BR>From: petercon@microsoft.com<BR>To: cewcathar@hotmail.com; ietf-languages@iana.org<BR>Subject: RE: Criteria for languages<BR>Date: Wed, 9 Dec 2009 07:58:36 +0000<BR><BR><BR>
<STYLE>
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.ecxMsoHyperlinkFollowed
{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 p.ecxMsoListParagraph, .ExternalClass li.ecxMsoListParagraph, .ExternalClass div.ecxMsoListParagraph
{margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass span.ecxHTMLPreformattedChar
{font-family:Consolas;}
.ExternalClass span.ecxEmailStyle20
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;}
.ExternalClass div.ecxWordSection1
{page:WordSection1;}
.ExternalClass ol
{margin-bottom:0in;}
.ExternalClass ul
{margin-bottom:0in;}
</STYLE>
<DIV class=ecxWordSection1>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">> The basic intent of macrolanguages in ISO 639-3 (and extlang subtags in BCP 47 – the original idea for extended language subtags was related to the origination of macrolanguages) can be understood from the Chinese cases – a prototypical example: zh / zho had been in use for some time, and there was clear precedent for using that for not only Mandarin content but also for Cantonese, Wu and other varieties. (In fact, there were registrations under RFC 1766 that explicitly connected several of these to zh.) At the same time, “Chinese” had been perceived as an individual language, not a collection; yet clearly Cantonese etc. are reasonably deemed distinct languages.</SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">> Now, applying to some potential case (framing with certain assumptions): Suppose XXX is used for some developed language Lx and Ly is some less-developed language closely related to Lx; if Ly is being newly coded as YYY, then :</SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=ecxMsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><SPAN>> -<SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></SPAN></SPAN><SPAN dir=ltr></SPAN><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">If there is evidence indicating that XXX has been used reasonably widely (by some measure) for Ly, then it may make sense to rescope XXX as a macrolanguage entry that encompasses YYY (and an additional new entry XXX’ to denote the developed language Lx proper – exclusive of Ly)</SPAN></P>
<P class=ecxMsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><SPAN>> -<SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></SPAN></SPAN><SPAN dir=ltr></SPAN><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">In the absence of such evidence, it probably makes most sense to deem XXX as denoting only Lx, in which case the scope of XXX is unchanged</SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">> Now, if the first case applies, and XXX becomes deemed a macrolanguage, then (and only then) do we here have a potential option to register YYY (and XXX’) as an extlang. (Though John has, I think, been arguing that this is a hypothetical option only, and not a real option under an assumed interpretation of RFC 5646.)</SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">> Peter</SPAN></P>
<P class=ecxMsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P></DIV> </body>
</html>