<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: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=us-ascii">
<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;}
/* 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:1.0in 1.0in 1.0in 1.0in;}
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 think there may be some misunderstanding: the JAC is *<b>not</b>*
discussing creation of a new tag; rather, they are discussing the addition of “not
applicable” as an alternate term describing “zxx”. <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'><o:p> </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> </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"'> Karen_Broome@spe.sony.com
[mailto:Karen_Broome@spe.sony.com] <br>
<b>Sent:</b> Wednesday, March 19, 2008 8:40 PM<br>
<b>To:</b> Peter Constable<br>
<b>Cc:</b> ietf-languages@iana.org<br>
<b>Subject:</b> RE: ID for language-invariant strings<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>I hope I haven't made the
situation worse, but it appears that the JAC has discussed this before and it
sounds like they will support the "not applicable" tag -- I was told
the turnaround shouldn't be nearly as long as I've waited for other requests --
but that they think it should be a new tag. I don't know if anyone here can
convince the JAC otherwise. (I don't know who on this list actually gets to
weigh in on 639-2.) I'm OK with a new tag, though I would have preferred a
broadening.<br>
<br>
In my opinion, I've never seen a real use case for zxx that wasn't better
served by the semantic "not applicable." <br>
<br>
Regards,<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Karen Broome<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><span style='color:#990099'>-----ietf-languages-bounces@alvestrand.no
wrote: -----<br>
<br>
</span>>To: "ietf-languages@iana.org" <ietf-languages@iana.org><br>
>From: Peter Constable <petercon@microsoft.com><br>
>Sent by: ietf-languages-bounces@alvestrand.no<br>
>Date: 03/19/2008 08:23PM<br>
>Subject: RE: ID for language-invariant strings<br>
><br>
>Here's where I see this discussion having come to:<br>
><br>
>- There was some agreement that it would be good to document a<br>
>recommended tag for reference-name scenarios such as the one I<br>
>described.<br>
><br>
>- It led to a tangential proposal that the denotation of "zxx"
could<br>
>be broadened to 'not applicable' (Karen is following up with the<br>
>JAC).<br>
><br>
>- There was general opposition to a new code element for<br>
>reference-name scenarios such as the one I described (Randy indicated<br>
>some support but several were opposed).<br>
><br>
>- There was *not*, however, any consensus as to *what* code element<br>
>should be used for reference-name scenarios.<br>
><br>
><br>
>At this point, since I need to move forward on drafting text for<br>
>OpenType, it appears I need to make my own choice between "und"
and<br>
>"zxx" for OpenType reference names.<br>
><br>
><br>
><br>
>Peter<br>
>_______________________________________________<br>
>Ietf-languages mailing list<br>
>Ietf-languages@alvestrand.no<br>
>http://www.alvestrand.no/mailman/listinfo/ietf-languages<br>
><br>
><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>