That may or may not be a reason for a registrant to decide it isn't worth registering, but not a protocol problem.<br><br clear="all">Mark<br>
<br><br><div class="gmail_quote">2009/3/23 Erik van der Poel <span dir="ltr"><<a href="mailto:erikv@google.com">erikv@google.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;">
I'd be more concerned about the "side of the bus" issue. If there is<br>
an ad for aujourd'<a href="http://hui.fr" target="_blank">hui.fr</a> on the side of a bus, and a user tried to<br>
type that on a French keyboard (or an American tourist's laptop),<br>
would a typical app assume U+0027 or U+2019?<br>
<br>
Erik<br>
<br>
2009/3/23 Mark Davis <<a href="mailto:mark@macchiato.com">mark@macchiato.com</a>>:<br>
<div><div></div><div class="h5">> Why would a script care about U+2019, any more than any other non-ASCII<br>
> character?<br>
><br>
> Mark<br>
><br>
><br>
> 2009/3/23 Patrik Fältström <<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>><br>
>><br>
>> I can think of many cases where the apostrophe and other characters are<br>
>> part of domain names given back when looking up PTR records in DNS, the<br>
>> hostname gets added to a logfile (as a U-label) and then later parsed by a<br>
>> script.<br>
>><br>
>> Patrik<br>
>><br>
>> On 20 mar 2009, at 09.44, Vint Cerf wrote:<br>
>><br>
>>> I am not aware of any, Mark, but perhaps others are?<br>
>>><br>
>>> Vint Cerf<br>
>>> Google<br>
>>> 1818 Library Street, Suite 400<br>
>>> Reston, VA 20190<br>
>>> 202-370-5637<br>
>>> <a href="mailto:vint@google.com">vint@google.com</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> On Mar 20, 2009, at 12:27 PM, Mark Davis wrote:<br>
>>><br>
>>>> Have there been any problems with apostrophe (U+2019) since IDNA2003 was<br>
>>>> deployed, or can you spell out a scenario where an apostrophe would cause a<br>
>>>> problem?<br>
>>>><br>
>>>> Mark<br>
>>>><br>
>>>><br>
>>>> 2009/3/20 Patrik Fältström <<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>><br>
>>>> On 19 mar 2009, at 21.31, Mark Davis wrote:<br>
>>>><br>
>>>> There has been no uproar about<br>
>>>> the fact that IDNA2008 disables many, many names in English (especially<br>
>>>> Irish), French, Italian, and others. For example, all of the following<br>
>>>> are<br>
>>>> currently allowed in IDNA, but would be disallowed under IDNA2008.<br>
>>>><br>
>>>> FWIW, allowing anything that looks like (yes, I use that non-specific<br>
>>>> phrase very intentional) a character that is dangerous in scripting is and<br>
>>>> was when IDNA2003 was created a very very very bad idea. I do not think many<br>
>>>> people see the difference between ’ and ', and allowing such characters and<br>
>>>> %, !, $, * etc is something I would say is a bad idea. Very bad idea. Not<br>
>>>> everyone can have "their name" as a domain name. Because domain names are<br>
>>>> domain names, and not words and names.<br>
>>>><br>
>>>> That said, I see your point regarding already registered domain names.<br>
>>>> Same thing for domain names that include arrows, snowman etc.<br>
>>>><br>
>>>> Patrik<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>
>>><br>
>><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>
><br>
><br>
</div></div></blockquote></div><br>