<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
> Add, to show that we not playing favorites, "Even the very<br>
> common words in English like "can't, and "don't" are not allowed.<br>
<br>
</div>...won't work for me, I'm not sure that "don't" is a "word".<br>
<br>
Of course English is favoured, pretending that it's not is a<br>
waste of everybody's time. And it starts to get surreal if<br>
folks say "Roman alphabet" when they mean "US-ASCII letters"<br>
for political correctness, nothing is wrong with "w" and "u".</blockquote><div><br>For historical reasons, English does have a special place in DNS. The purpose of IDNA is to erase that distinction as much as possible, allowing characters needed by any language. The point here is not about that general issue, but that *not every character that people thinks are part of words in a language* is necessarily going to be in IDNA. And as an example of that, even English in its 'special' position does not get perfectly ordinary, common words like "don't".<br>
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Frank<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>
</blockquote></div><br>