Vint,<br>I think Alireza expresses a position that linguistic TLD Managers and Registry Managers can only share. The IDNA proposition as it turns to become does not offer the e-empowerment capacity languages desserve, users expect, and standards and Gov. demand.<br>
<br>The same as I consider that French support must be discussed by authoritative French linguists and ISO standard organization (AFNOR), I can only trust the Arabic language experts who formed a dedicated mailing list. The same as trust CJK experts to discuss their languages.<br>
<br>If DISALLOW means "DISALLOW for the xn-- IDNA2008 English ASCII users version", it is to the English speakers to decide.<br><br>However, we must accept that it means that linguistic TLD project Managers will start considering their own "x.--" versions (what this WG seems to push for) or extension (what I plea for).<br>
<br>Since I am not sure that the people who answered YES realized this, I will answer NO.<br><br>Not NO about a specifc code point I never used in my life, but for the fundamental position of this WG to clearly be spelled out before:<br>
<br>- either IDN2008 is an English ASCII oriented version which does not consider interoperability with other linguistic communities solutions (?) <br>- or a default, which wants to support interoperability with other lingustic community solutions (?). <br>
<br>jfc<br><br><br><br><br><br><div class="gmail_quote">2009/3/23 Alireza Saleh <span dir="ltr"><<a href="mailto:saleh@nic.ir">saleh@nic.ir</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
No,<br>
<br>
I think this is the registry choice to make it DISALLOW.<br>
if you search Arabic-script you will find more examples that are not<br>
essential for language and may also be considered that they are only for<br>
typography reasons. These codes are also PVALID under IDNA2008 policy.<br>
I'm sure if the group put them for vote they will also have the same<br>
ending as Tatweel ( Consider U+0651). In that situation I suggest to<br>
disallow all characters in all scripts and then choose a list of allowed<br>
characters among them. The name of the protocol could be changed to IDNA<br>
for English users.<br>
<br>
Alireza<br>
<div class="im"><br>
Mark Davis wrote:<br>
> My apologies, could you reissue this call for both characters? I've<br>
> confirmed that they share the same characteristics.<br>
><br>
</div>> |U+0640 <<a href="http://unicode.org/cldr/utility/character.jsp?a=0640" target="_blank">http://unicode.org/cldr/utility/character.jsp?a=0640</a>>|<br>
> ( ـ ) ARABIC TATWEEL<br>
> |U+07FA <<a href="http://unicode.org/cldr/utility/character.jsp?a=07FA" target="_blank">http://unicode.org/cldr/utility/character.jsp?a=07FA</a>>|<br>
<div class="im">> ( ߺ ) NKO LAJANYALAN<br>
><br>
> Mark<br>
><br>
><br>
> On Sun, Mar 22, 2009 at 08:32, Vint Cerf <<a href="mailto:vint@google.com">vint@google.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:vint@google.com">vint@google.com</a>>> wrote:<br>
><br>
> Based on the on-line exchanges, it appears to me that the general<br>
> consensus is to ban TATWEEL by exception (ie. make it DISALLOWED).<br>
><br>
> Please respond with:<br>
><br>
> YES (ie make it DISALLOWED)<br>
><br>
> NO (ie leave it PVALID)<br>
><br>
> OTHER: <explain what you propose><br>
><br>
> I will tally the responses arriving by April 4, midnight, EDT.<br>
><br>
><br>
><br>
> Vint Cerf<br>
> Google<br>
> 1818 Library Street, Suite 400<br>
> Reston, VA 20190<br>
> 202-370-5637<br>
</div>> <a href="mailto:vint@google.com">vint@google.com</a> <mailto:<a href="mailto:vint@google.com">vint@google.com</a>><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Idna-update mailing list<br>
> <a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a> <mailto:<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a>><br>
<div class="im">> <a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><br>
> _______________________________________________<br>
> Idna-update mailing list<br>
> <a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
> <a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
><br>
<br>
_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</div></div></blockquote></div><br>