I'm glad you can live with it (If someone wanted to simulate O'Reilly, there are many other ways to do it, so that shouldn't make a difference for this particular one).<br><br clear="all">Mark<br>
<br><br><div class="gmail_quote">2009/7/16 John C Klensin <span dir="ltr"><<a href="mailto:klensin@jck.com">klensin@jck.com</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;">
<br>
<br>
--On Thursday, July 16, 2009 03:43 -0700 Michel SUIGNARD<br>
<div class="im"><<a href="mailto:Michel@suignard.com">Michel@suignard.com</a>> wrote:<br>
<br>
> I agree with the position expressed here. As long as 02B9 is<br>
> allowed/requested in some context, it is just as easy to allow<br>
> it in the protocol. Context conditions are just too<br>
> complicated for that character and are bound to be<br>
> controversial. I am too enthused though because of its<br>
> resemblance to apostrophe (0027), but on the other end it will<br>
> make supporters of many writing systems very happy.<br>
<br>
</div>I can live with this, but assume that it will lead directly to<br>
labels that contain<br>
O<U+02B9>Reilly<br>
in order to simulate<br>
O'Reilly<br>
<br>
The perceived availability of such labels in the protocol will<br>
almost certainly cause demands to permit that sort of<br>
arrangement in SLDs and TLDs, not just down in the tree where<br>
enterprises make up their own rules. Since operating systems<br>
won't parse it as an apostrophe or single quote, maybe there<br>
will be no significant damage, but it makes me very anxious<br>
indeed.<br>
<font color="#888888"><br>
john<br>
</font><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>
</div></div></blockquote></div><br>