The real issue: interopability, and a proposal (Was: Consensus Call on Latin Sharp S and Greek Final Sigma)
Shawn.Steele at microsoft.com
Tue Dec 1 18:22:03 CET 2009
I think that's Mark's point. He was following the previous logic and saying that if you can't map PVALID, then you shouldn't map DISALLOWED because they could become PVALID. Eg: effectively what's happening to eszett.
From: idna-update-bounces at alvestrand.no [idna-update-bounces at alvestrand.no] on behalf of Alexander Mayrhofer [alexander.mayrhofer at nic.at]
Sent: Tuesday, December 01, 2009 9:10 AM
To: Mark Davis ☕; Vint Cerf
Cc: Shawn Steele; patrik at frobbit.se; harald at alvestrand.no; idna-update at alvestrand.no; lisa.dusseault at gmail.com; duerst at it.aoyama.ac.jp
Subject: RE: The real issue: interopability, and a proposal (Was: Consensus Call on Latin Sharp S and Greek Final Sigma)
> 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", 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.
Idna-update mailing list
Idna-update at alvestrand.no
More information about the Idna-update