- From: Mounir Lamouri <mounir.lamouri@gmail.com>
- Date: Fri, 04 Feb 2011 12:47:58 +0100
On 02/04/11 11:55, Anne van Kesteren wrote: > This must have been brought up before as e.g. > http://pukupi.com/post/2070/ is from June 2010, but I could not find > anything quickly. Apparently people are using IDNs and cannot get them > validated with email controls because the specification prohibits this. > We should probably change that. Either by saying it should first be > converted to Punycode and then validated, or by enhancing the pattern. > (The email RFC might still be outdated on this point, I have not > checked, but we have decided to not follow it anyway as it fails to > match email addresses people actually use.) As far as I understand it, the specification somewhat handles this by telling UAs they "may" puny-encode/decode the value to show the IDN value and still be able to validate it with the current rules [1]. Note that there is a bug open to make this "may" a "should" or a "must" [2]. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#e-mail-state [2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=11579 -- Mounir
Received on Friday, 4 February 2011 03:47:58 UTC