Dear Erik,<div>I am not sure of the Internet and Internet users you talk about.</div><div>May be will you want to access <a href="http://i-dns.net">http://i-dns.net</a>?</div><div>jfc</div><div><br></div><div><br></div><div>
<br><div class="gmail_quote">2009/3/15 Erik van der Poel <span dir="ltr"><<a href="mailto:erikv@google.com">erikv@google.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> The percentage of IE6 users who downloaded the VeriSign plug-in in<br>
> order to access IDN-labeled resources was 100%.<br>
<br>
</div>:-)<br>
<br>
Yes, but what percentage of the users that were redirected to the<br>
plug-in download page actually downloaded it?<br>
<div class="im"><br>
>> I'm not sure whether Eszett users are clamoring for IDNAbis. Perhaps<br>
>> the Greeks are, but not because of Final Sigma. They want to solve<br>
>> their tonos problem. And I have to agree that ZWJ/ZWNJ users seem to<br>
>> be clamoring for IDNAbis.<br>
><br>
> How on earth did IDNA2008 become a matter of providing support for this<br>
> handful of code points?<br>
<br>
</div>I confess that I am overly focussed on this handful, primarily because<br>
of compatibility issues.<br>
<br>
Let's hope that if anybody creates plug-ins for IDNA2008, that they<br>
implement them carefully and avoid further compatibility problems. The<br>
IDNA2003 plug-ins exacerbated the Eszett/FinalSigma/ZWJ/ZWNJ problem<br>
by performing those mappings on strings that are interchanged (HTML<br>
hrefs), rather than limiting those mappings to the keyboard UI.<br>
<br>
If IDNA2008 plug-ins start performing multiple lookups, we will<br>
probably see HTML files start to take advantage of that. Then, when<br>
the browser developers get around to implementing IDNA2008, they may<br>
feel compelled to perform multiple lookups too, just to make those new<br>
HTML files "work".<br>
<br>
Of course, this WG's intention is to use multiple lookup as a<br>
transition strategy, but if HTML files and Web sites that rely on the<br>
"old" lookup don't disappear completely, the browser developers may<br>
feel compelled to continue the multiple lookups, perhaps forever.<br>
Programmers often add features, but are scared to remove features, for<br>
fear of "breaking" something.<br>
<br>
This is pretty common on the Web. The browsers are too lenient, and so<br>
they end up having to support the Web sites and HTML files that take<br>
advantage of that leniency forever.<br>
<br>
Maybe I'm too pessimistic here, but I am quite concerned about multiple lookup.<br>
<font color="#888888"><br>
Erik<br>
</font><div><div></div><div class="h5">_______________________________________________<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></div>