<br><font size=2 face="sans-serif">Looks good to me.<br>
<br>
Shalom (Regards), Mati<br>
Bidi Architect<br>
Globalization Center Of Competency
- Bidirectional Scripts<br>
IBM Israel<br>
Phone: +972 2 5888802 Fax:
+972 2 5870333 Mobile: +972 52 2554160<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Harald Tveit Alvestrand
<harald@alvestrand.no></b> </font>
<p><font size=1 face="sans-serif">06/08/2009 13:18</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">Matitiahu Allouche/Israel/IBM@IBMIL</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">idna-update@alvestrand.no</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: comments on draft-ietf-idnabis-bidi</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>When integrating comments into text, some additional
notes....<br>
<br>
<br>
>> 12) The next sentence says: "In a domain name consisting
of only <br>
>> LDH-labels and labels that pass the test, the requirements of
Section <br>
>> 3 are satisfied as long as a label that starts with an ASCII digit
<br>
>> does not come after a right-to-left label that ends in a digit."<br>
>> This is not true. See example b above.<br>
>> <br>
> You are right. This needs to be documented; I did not test this case.<br>
> <br>
I changed the sentence to say "the requirements of Section<br>
<br>
3 are satisfied as long as a label that starts with an ASCII digit <br>
does not come after a right-to-left label" - I think this is true
for all cases.<br>
<br>
>> 13) In section 3, there appears the sentence: "the label
"123-456" <br>
>> will have a different display order in an RTL context than in
a LTR <br>
>> context."<br>
>> This is not true, IMHO. If the last letter before the label
is not an <br>
>> Arabic Letter, it will be displayed as "123-456" both
in LTR and RTL <br>
>> context. If it is an Arabic Letter, it will be displayed
as "456-123".<br>
>> <br>
> I will have to test this. Thanks for pointing it out.<br>
> <br>
Hm. When I looked at my code, I even had a test for this case, and you
<br>
are right.<br>
However, I think I found the example I was trying to reconstruct - the
<br>
label (network order)<br>
"12-a" will display as "12-a" in LTR, and "a-12"
in RTL. This, however, <br>
is already a non-permitted label.<br>
<br>
>> 14) In section 3, there appears the sentence: "The Label
Uniqueness <br>
>> property should hold true between LTR paragraphs and RTL paragraphs.
<br>
>> This was shown to be unsound."<br>
>> In fact, in all cases where Character Grouping and Label Uniqueness
<br>
>> are satisfied for each paragraph direction separately, there will
be <br>
>> Label Uniqueness between LTR and RTL paragraphs.<br>
>> <br>
> I will have to test this. I think a fairly common case was found (ALEPH
<br>
> 1 / 1 ALEPH comes to mind, but 1 ALEPH is disallowed). Since this
was <br>
> ruled out of context early on, I don't think either my code or Erik's
<br>
> code checks for this at the moment.<br>
> <br>
After contemplating this for a while, I'm deleting the paragraph.<br>
<br>
I'm also putting in the rules you suggested in a later message.<br>
<br>
Harald<br>
</font></tt>