<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>(How'd this thread lose UTF-8)?</div>
<div> </div>
<div>> It isn't that you can't use a sharp-s or a final sigma in IDNA2003. You</div>
<div>> just can't make a domain name *distinction* from "ss" or medial sigma,</div>
<div>> respectively, for them.</div>
<div> </div>
<div>Yes, I think that's well said. I'd also like to point out that just because you can't make a distinction does NOT mean that the newly PVALID forms must somehow magically turn into the IDNA2003 forms. </div>
<div> </div>
<div>Eg: I'm not trying to say that if you want Eszett you should be forced to end up with ss. It may be that for one domain (wei<font face="Calibri Greek">β</font> maybe) Eszett is appropriate for correct spelling, and a different domain (strauss maybe),
ss is appropriate for correct spelling. Those two can coexist (wei<font face="Calibri Greek">β</font> & strauss), but you can't differentiate between the other forms (wei<font face="Calibri Greek">β</font> & weiss.)</div>
<div> </div>
<div>I further think the indications are that if they could co-exist, then people that might care would bundle them anyway, making the distinction moot. However even that doesn't change that someone wants <font face="Calibri Greek">β</font> spelled with an
<font face="Calibri Greek">β</font> and not an ss, and I think it's quite important that we enable them to spell their domain correctly.</div>
<div> </div>
<div>- Shawn</div>
<div> </div>
<div> </div>
</span></font>
</body>
</html>