> This is a problem, but not an unsolvable one. Browsers will support PUNYCODE > AND be safe eventually.
You are right, that it is more complicated than I initially mentioned, however, chromium has pretty much decided already which way they are going to go. Don't hold your breath waiting for √.com to be supported, because in the design documents it is something they won't fix. There is a nice summary at the bottom, and you will see that Google has chosen to go the same route as Microsoft. My guess is that Safari will become more secure like Chrome/IE/Firefox, not the other way around. see: http://www.chromium.org/developers/design-documents/idn-in-google-chrome > Cheers, > > tedd > > _____________________ > t...@sperling.com > http://sperling.com > > > > > > > > _______________________________________________ > New York PHP Users Group Community Talk Mailing List > http://lists.nyphp.org/mailman/listinfo/talk > > http://www.nyphp.org/Show-Participation _______________________________________________ New York PHP Users Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/Show-Participation
