The real issue: interopability, and a proposal (Was: Consensus Call on Latin Sharp S and Greek Final Sigma)

Mark Davis ☕ mark at macchiato.com
Tue Dec 1 18:55:46 CET 2009


My apologies to all. I had meant to write:

To be complete, one would ban mapping not only of PVALID, but also of *
UNASSIGNED* (since those are in an indeterminate state, and could become
PVALID).

Sorry for the confusion!

Mark


On Tue, Dec 1, 2009 at 09:10, Alexander Mayrhofer <
alexander.mayrhofer at nic.at> wrote:

> > To be complete, one would ban mapping not only of PVALID, but
> > also of DISALLOWED (since those are in an indeterminate
> > state, and could become PVALID).
>
> I strongly oppose that.
>
> Disallowing mappings of DISALLOWED characters (sic) would mean that user
> input in the form of "Äpfel.at" (apples) could not be mapped to "äpfel.at<http://xn--pfel-koa.at>",
> because "Ä" (like any other uppercase non-ASCII character) is DISALLOWED.
>
> 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.
>
> Alex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/idna-update/attachments/20091201/e57beeb5/attachment.htm 


More information about the Idna-update mailing list