| Now look, seriously, there is *no* *freakin* *way* that we can go to | just-do-UTF-8. At the very least resolvers need to know about the | difference between wide() and normal names, systems need $HOSTNAME calls | that support UTF-8 encodings, etc. This is a massive undertaking. The 'just send UTF-8' approach also ignores the normalization issues addressed by nameprep, unless you think, as Bill Semich has suggested, that a protocol based on nameprep only somehow makes sense and is actually deployable. -bws
- Re: [idn] Why we can go directly to UTF-8 Martin Duerst
- Re: [idn] Why we can go directly to UTF-8 Eric A. Hall
- Re: [idn] Why we can go directly to UTF-8 Keith Moore
- Re: [idn] Why we can go directly to UTF-8 D. J. Bernstein
- Re: [idn] Why we can go directly to UTF-8 Eric A. Hall
- Re: [idn] Why we can go directly to UTF-8 Eric A. Hall
- Re: [idn] Why we can go directly to UTF-8 Brian W. Spolarich
- Re: [idn] Why we can go directly to UTF-8 D. J. Bernstein
- Re: [idn] Why we can go directly to UTF-8 Eric A. Hall
- Re: [idn] Why we can go directly to UTF-8 James Seng/Personal
- Re: [idn] Why we can go directly to UTF-8 James Seng/Personal
