<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 08/10/2011 10:29 AM, Abdulrahman I. ALGhadir wrote:
<blockquote
cite="mid:E393942FC3AB7F4C9C50F559E9E4E45F13AE64F9@ry2mail2.citc.gov.sa"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<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;}
@font-face
{font-family:"Courier New \; color\: black\;";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Well
in this case the protocol didn’t give any standard solution
way to handle this problem rather letting it to be treated
as vendor wish (shouldn’t the rfc enacts in making
standards) or at least to acknowledge this issue and to push
it to another level e.g. Unicode URI rendering?</span></p>
</div>
</blockquote>
<br>
The group discussed the problem of detecting the presence of domain
names in free text, and the consequences of having domain names
display differently when apps treated them as domain names and when
apps treated them as free text.<br>
<br>
The conclusion was that detecting domain names in free text is just
about impossible, and that consistent behaviour is important to
users; thus, the WG did not recommend any special treatment for
domain names, choosing rather to live with the results of the
existing BIDI algorithm.<br>
<br>
<blockquote
cite="mid:E393942FC3AB7F4C9C50F559E9E4E45F13AE64F9@ry2mail2.citc.gov.sa"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0cm 0cm;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;">From:</span></b><span style="font-size:
10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;"> <a class="moz-txt-link-abbreviated" href="mailto:idna-update-bounces@alvestrand.no">idna-update-bounces@alvestrand.no</a>
[<a class="moz-txt-link-freetext" href="mailto:idna-update-bounces@alvestrand.no">mailto:idna-update-bounces@alvestrand.no</a>]
<b>On Behalf Of </b>Harald Alvestrand<br>
<b>Sent:</b> 7/Aug/2011 11:55 PM<br>
<b>To:</b> Abdulrahman I. ALGhadir<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a><br>
<b>Subject:</b> Re: mixing different direction labels
within same domain<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On 06/21/11 07:55, Abdulrahman I. ALGhadir
wrote: <o:p></o:p></p>
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal">I am just wondering whenever it is
permitted or not to have this case:<o:p></o:p></p>
<p class="MsoNormal"><r2l
chars><num1>.<num2>.<etc ..><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt; font-family:
"Times New Roman","serif";">This
particular case has all labels legal, but the overall
display name will display very oddly (as noted). The oddity
is caused by our inability to mandate whole-domain tests, as
described in the RFC.<br>
<br>
It is logical for the administrator of <etc ..> to
forbid registration of leading-numeric labels if it
anticipates R2L labels at the next level down, and it is
logical for application writers to simply reject such names
because they are going to confuse the users (much in the
spirit of Firefox' refusal to do mixed-script names), but
the RFC does not require them to do so.<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal">As you know in case r2l labels the display
will be like this<o:p></o:p></p>
<p class="MsoNormal"><etc..>.<num1>.<num2><r2l
chars><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt; font-family:
"Times New Roman","serif";">I think the
display will depend on the direction of <etc> and
whether it is in an RTL context or an LTR context, but I'm
still not confident of my ability to execute the BIDI
algorithm in my head.<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal">As you see both of them have different
display order which isn’t the same as network order.<o:p></o:p></p>
<p class="MsoNormal">And I know it is mentioned in the RFC <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<pre><span dir="RTL"></span><span dir="RTL" lang="AR-SA"><span dir="RTL"></span> </span>Several stronger statements were considered and rejected, because<o:p></o:p></pre>
<pre><span dir="RTL"></span><span dir="RTL" lang="AR-SA"><span dir="RTL"></span> </span>they seem to be <b>impossible to fulfill within the constraints of the</b><o:p></o:p></pre>
<pre><span dir="RTL"></span><b><span dir="RTL" lang="AR-SA"><span dir="RTL"></span> </span>Unicode bidirectional algorithm</b><span dir="RTL"></span><span dir="RTL" lang="AR-SA"><span dir="RTL"></span>.</span><o:p></o:p></pre>
<p class="MsoNormal"><span style="font-family:
"Arial","sans-serif";"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:
"Arial","sans-serif";">And one of the
statement is
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:
"Arial","sans-serif";"> </span><o:p></o:p></p>
<p class="MsoNormal"><span dir="RTL"></span><span dir="RTL"
style="font-family:
"Arial","sans-serif";" lang="AR-SA"><span
dir="RTL"></span> </span><span style="font-size: 10pt;
font-family: "Courier New ; color:
black;","serif";">o</span><span dir="RTL"></span><span
dir="RTL" style="font-size: 10pt; font-family: "Times
New Roman","serif";" lang="AR-SA"><span
dir="RTL"></span>
</span><span style="font-size: 10pt; font-family:
"Courier New ; color: black;","serif";">The
sequence of labels should be consistent with network order</span><span
dir="RTL"></span><span dir="RTL" style="font-size: 10pt;
font-family: "Times New Roman","serif";"
lang="AR-SA"><span dir="RTL"></span>.</span><o:p></o:p></p>
<p class="MsoNormal"><span dir="RTL"></span><span dir="RTL"
style="font-size: 10pt; font-family: "Courier
New";" lang="AR-SA"><span dir="RTL"></span>
</span><span style="font-size: 10pt; font-family:
"Courier New";">This proved impossible -- a domain
name consisting of the labels</span><o:p></o:p></p>
<p class="MsoNormal"><span dir="RTL"></span><span dir="RTL"
style="font-size: 10pt; font-family: "Courier
New";" lang="AR-SA"><span dir="RTL"></span>
</span><span style="font-size: 10pt; font-family:
"Courier New";">in network order) L1.R2.R3.L4 will
be displayed as L1.R3.R2.L4 in</span><o:p></o:p></p>
<p class="MsoNormal"><span dir="RTL"></span><span dir="RTL"
style="font-size: 10pt; font-family: "Courier
New";" lang="AR-SA"><span dir="RTL"></span>
</span><span style="font-size: 10pt; font-family:
"Courier New";">an LTR context<span dir="RTL"></span><span
dir="RTL" lang="AR-SA"><span dir="RTL"></span>. (</span>In
an RTL context, it will be displayed as</span><o:p></o:p></p>
<p class="MsoNormal"><span dir="RTL"></span><span dir="RTL"
style="font-size: 10pt; font-family: "Courier
New";" lang="AR-SA"><span dir="RTL"></span>
</span><span style="font-size: 10pt; font-family:
"Courier New";">L4.R3.R2.L1<span dir="RTL"></span><span
dir="RTL" lang="AR-SA"><span dir="RTL"></span>)</span></span><o:p></o:p></p>
<p class="MsoNormal" dir="RTL" style="text-align: right;
direction: rtl; unicode-bidi: embed;">
<span dir="RTL"></span><span style="font-family:
"Arial","sans-serif";" lang="AR-SA"><span
dir="RTL"></span> </span><span dir="LTR"><o:p></o:p></span></p>
<pre dir="RTL" style="text-align: right; direction: rtl; unicode-bidi: embed;"><span dir="RTL"></span><span style="font-size: 11pt; font-family: "Arial","sans-serif"; color: rgb(31, 73, 125);" lang="AR-SA"><span dir="RTL"></span> </span><span lang="AR-SA"><o:p></o:p></span></pre>
<p class="MsoNormal"><span dir="RTL" style="font-family:
"Arial","sans-serif";" lang="AR-SA"> </span><span
dir="RTL" style="font-family: "Times New
Roman","serif";" lang="AR-SA"><o:p></o:p></span></p>
<p class="MsoNormal">And I have tried two implemented tools
(well I don’t know if they follow the RFC fully or not).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p><span style="font-size: 10pt; font-family:
"Tahoma","sans-serif";"><a
moz-do-not-send="true"
href="http://unicode.org/cldr/utility/idna.jsp?a=%D8%B1%D8%A7%D8%A6%D8%AF888.999.%D8%A7%D9%84%D8%B3%D8%B9%D9%88%D8%AF%D9%8A%D8%A9#notes">http://unicode.org/cldr/utility/idna.jsp?a=%D8%B1%D8%A7%D8%A6%D8%AF888.999.%D8%A7%D9%84%D8%B3%D8%B9%D9%88%D8%AF%D9%8A%D8%A9#notes</a></span><o:p></o:p></p>
<p><span style="font-size: 10pt; font-family:
"Tahoma","sans-serif";"><a
moz-do-not-send="true"
href="http://mct.verisign-grs.com/conversiontool/convertServlet?input=%D8%B1%D8%A7%D8%A6%D8%AF888.999.%D8%A7%D9%84%D8%B3%D8%B9%D9%88%D8%AF%D9%8A%D8%A9&type=UTF8">http://mct.verisign-grs.com/conversiontool/convertServlet?input=%D8%B1%D8%A7%D8%A6%D8%AF888.999.%D8%A7%D9%84%D8%B3%D8%B9%D9%88%D8%AF%D9%8A%D8%A9<span
dir="RTL"></span><span dir="RTL" lang="AR-SA"><span
dir="RTL"></span>&</span>type=UTF8</a></span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Abdulrahman,<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Idna-update mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.alvestrand.no/mailman/listinfo/idna-update">http://www.alvestrand.no/mailman/listinfo/idna-update</a><o:p></o:p></pre>
<p class="MsoNormal"><span style="font-size: 12pt; font-family:
"Times New Roman","serif";"><o:p> </o:p></span></p>
</div>
</blockquote>
<br>
</body>
</html>