My apologies to all. I had meant to write:<br><br><div style="margin-left: 40px;">To be complete, one would ban mapping not only of PVALID, but also of <b>UNASSIGNED</b> (since those are in an indeterminate state, and could become
PVALID).<br></div><br>Sorry for the confusion!<br><br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Tue, Dec 1, 2009 at 09:10, Alexander Mayrhofer <span dir="ltr"><<a href="mailto:alexander.mayrhofer@nic.at">alexander.mayrhofer@nic.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> To be complete, one would ban mapping not only of PVALID, but<br>
> also of DISALLOWED (since those are in an indeterminate<br>
> state, and could become PVALID).<br>
<br>
</div>I strongly oppose that.<br>
<br>
Disallowing mappings of DISALLOWED characters (sic) would mean that user input in the form of "Äpfel.at" (apples) could not be mapped to "<a href="http://xn--pfel-koa.at" target="_blank">äpfel.at</a>", because "Ä" (like any other uppercase non-ASCII character) is DISALLOWED.<br>
<br>
I think that the very objective of mappings is to deal with DISALLOWED characters. Not allowing that would essentially remove the purpose of the mapping itself.<br>
<br>
Alex<br>
</blockquote></div><br>