<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 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 3 0 0 0 0 0 0 0;}
@font-face
{font-family:PMingLiU;
panose-1:2 2 3 0 0 0 0 0 0 0;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 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:"Lucida Sans Unicode";
panose-1:2 11 6 2 3 5 4 2 2 4;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 2 3 0 0 0 0 0 0 0;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</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'>I don’t think obfuscation is good at all, which is why I’m
against changing the other subtags and think that abbreviated subtags should be
avoided when ample room exists for a completely spelled out subtag. However, a
native term for “classical Sanskrit” would possibly be useful as a way of
avoiding folks tagging stuff like “el-classic” or “de-classic”.<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:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Addison Phillips<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Globalization Architect </span><span style='font-size:9.0pt;
font-family:"Lucida Sans Unicode","sans-serif";color:#1F497D'>(Lab126)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Chair (W3C I18N, IETF IRI WGs)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Internationalization is not a feature.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>It is an architecture.<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>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<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"'>
mark.edward.davis@gmail.com [mailto:mark.edward.davis@gmail.com] <b>On Behalf
Of </b>Mark Davis ?<br>
<b>Sent:</b> Tuesday, July 13, 2010 10:41 AM<br>
<b>To:</b> Phillips, Addison<br>
<b>Cc:</b> Doug Ewell; ietf-languages@iana.org; peter_scharf@brown.edu<br>
<b>Subject:</b> Re: Language Variant subtags for Sanskrit<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Georgia","serif"'>I fail to
understand why people think that obfuscation is a good thing... There will be a
prefix for "classical" that completely disambiguates it.</span><o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Georgia","serif"'><br
clear=all>
</span>Mark<br>
<br>
— Il meglio è l’inimico del bene —<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, Jul 13, 2010 at 08:28, Phillips, Addison <<a
href="mailto:addison@lab126.com">addison@lab126.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>Most of the requests seem straightforward. Are we only
talking about the subtag for "classical"? Using a native term to
obfuscate "classical" would possibly be a good solution for that one
subtag. There is no reason why a native term is required for the others.<br>
<br>
Addison Phillips<br>
Globalization Architect (Lab126)<br>
Chair (W3C I18N, IETF IRI WGs)<br>
<br>
Internationalization is not a feature.<br>
It is an architecture.<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:ietf-languages-bounces@alvestrand.no">ietf-languages-bounces@alvestrand.no</a>
[mailto:<a href="mailto:ietf-languages-">ietf-languages-</a><br>
> <a href="mailto:bounces@alvestrand.no">bounces@alvestrand.no</a>] On
Behalf Of Doug Ewell<br>
> Sent: Tuesday, July 13, 2010 8:13 AM<br>
> To: <a href="mailto:ietf-languages@iana.org">ietf-languages@iana.org</a><br>
> Cc: <a href="mailto:peter_scharf@brown.edu">peter_scharf@brown.edu</a><br>
> Subject: Re: Language Variant subtags for Sanskrit<br>
><br>
> These requests for Sanskrit can't proceed until we have at least a<br>
> bit<br>
> of agreement on what the subtag values should be.<br>
><br>
> --<br>
> Doug Ewell | Thornton, Colorado, USA | <a href="http://www.ewellic.org"
target="_blank">http://www.ewellic.org</a><br>
> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s <br>
><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"
target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><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"
target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>