> The only way that UTF-8 IDNs will get into the legacy path is if a > particular implementation goes out of its way to use them where it > shouldn't. It will have to explicitly call the new API and then explicitly > pass data that is not supported by the application protocol. This scenario > is completely unrealistic. This is complete and utter nonsense, and I'm not going to dignify it further by continuing the discussion.
- Re: [idn] Debunking the ACE myth Keith Moore
- Re: [idn] Debunking the ACE myth Eric A. Hall
- Re: [idn] Debunking the ACE myth Keith Moore
- Re: [idn] Debunking the ACE myth Keith Moore
- Re: [idn] Debunking the ACE myth Eric A. Hall
- Re: [idn] Debunking the ACE myth Eric A. Hall
- Re: [idn] Debunking the ACE myth Keith Moore
- Re: [idn] Debunking the ACE myth Eric A. Hall
- Re: [idn] Debunking the ACE myth Patrik F�ltstr�m
- Re: [idn] Debunking the ACE myth David Hopwood
- Re: [idn] Debunking the ACE myth Keith Moore
- Re: [idn] Debunking the ACE myth David Hopwood
- Re: [idn] Debunking the ACE myth C C Magnus Gustavsson
- Re: [idn] Debunking the ACE myth Paul Hoffman / IMC
- Re: [idn] Debunking the ACE myth Adam M. Costello
- Re: [idn] Debunking the ACE myth Eric A. Hall
- Re: [idn] Debunking the ACE myth ned . freed
- Re: [idn] Debunking the ACE myth David Hopwood
- Re: [idn] Debunking the ACE myth Martin Duerst
- Re: [idn] Debunking the ACE myth Martin Duerst
- RE: [idn] Debunking the ACE myth Martin Duerst
