<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=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style id=owaParaStyle>
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: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;}
/* 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;
        margin:0in;
        margin-bottom:.0001pt;
        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;}
-->
</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'>Thanks for correcting the subject.<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'>Mapping ZWJ and ZWNJ to nothing (i.e. ignoring them) had issues
and that is why they were categorized as CONTEXTJ in the revised version and
allowed “on the wire” in the right context (after ACE conversion).
<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'>The IDNA implementation in different applications will catch up at
different pace. However that does not change the community requirements vis-à-vis
the protocol. Correct protocol representation also empowers communities to
develop their own applications.<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'>Regards,<br>
Sarmad<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>
<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"'> Shawn Steele
[mailto:Shawn.Steele@microsoft.com] <br>
<b>Sent:</b> Saturday, December 05, 2009 1:15 PM<br>
<b>To:</b> Shawn Steele; Sarmad Hussain; idna-update@alvestrand.no<br>
<b>Cc:</b> idna-arabicscript@lists.irnic.ir<br>
<b>Subject:</b> Re: Additional thoughts on TRANSITIONAL <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:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Oopsy, correcting subject.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>-Shawn<o:p></o:p></span></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:black'>
<hr size=2 width="100%" align=center>
</span></div>
<div id=divRpF388040>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> idna-update-bounces@alvestrand.no
[idna-update-bounces@alvestrand.no] on behalf of Shawn Steele
[Shawn.Steele@microsoft.com]<br>
<b>Sent:</b> Saturday, December 05, 2009 12:07 AM<br>
<b>To:</b> Sarmad Hussain; idna-update@alvestrand.no<br>
<b>Cc:</b> idna-arabicscript@lists.irnic.ir<br>
<b>Subject:</b> RE: Idna-update Digest, Vol 36, Issue 48</span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>I think that's true for all 4 characters. I don't think
we can disallow them.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>Note that ZWJ/ZWNJ can be used in a link in IDNA2003, but they're
mapped to nothing, so the address bar will likely look funny, though you can
still get to a server. I'm not saying that's good behavior, but I suppose
it's better than nothing. I'm also not trying to suggest it doesn't need
fixed, it is clearly a big display problem that should be addresses as soon as
practical.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>-Shawn<o:p></o:p></span></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:black'>
<hr size=2 width="100%" align=center>
</span></div>
<div id=divRpF592164>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>
idna-update-bounces@alvestrand.no [idna-update-bounces@alvestrand.no] on behalf
of Sarmad Hussain [sarmad.hussain@nu.edu.pk]<br>
<b>Sent:</b> Friday, December 04, 2009 7:50 PM<br>
<b>To:</b> idna-update@alvestrand.no<br>
<b>Cc:</b> idna-arabicscript@lists.irnic.ir<br>
<b>Subject:</b> Re: Idna-update Digest, Vol 36, Issue 48</span><span
style='color:black'><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'>> 200C ;
DISALLOWED # ZERO WIDTH NON-JOINER<br>
> 200D ; DISALLOWED # ZERO WIDTH JOINER<br>
><br>
> There is no new value called TRANSITIONAL. The infamous 4 characters<br>
> (above) start with the value DISALLOWED. Later, we change them to<br>
> PVALID (or CONTEXTJ for 200C/200D). <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'>Before reverting to IDNA2003 level
lack of support for these characters, do re-consider why the status of these
characters (ZWNJ and ZWJ) have been changed in Idnabis process: these
characters are required for writing IDNs for a billion people in South Asia and
beyond.<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'>Having them as DISALLOWED and
called TRANSITIONAL will only propagate older decisions, not fix them.
Having them as CONTEXTJ is already a workable solution, where they are
only (carefully) allowed, where they are needed. <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'>regards,<br>
Sarmad <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><br>
<br>
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3811 (20090129) __________<br>
<br>
The message was checked by ESET NOD32 Antivirus.<br>
<br>
<a href="http://www.eset.com">http://www.eset.com</a><o:p></o:p></p>
</div>
</div>
</body>
</html>