On Fri, 12 Jan 2001, Marc Blanchet wrote: | and the more "exotic" ( a friendly joke targetted to John K.): | directory, new class, etc... which, because of their property can use | or not encodings at all, more work to be done on that side tho. My working model has been that the IDN WG is going to come up with something to address current i18n needs, and that the 'exotic' stuff will be punted to a new WG. Am I close? :-) -bws
- [idn] Planning ahead for good IDNs D. J. Bernstein
- Re: [idn] Planning ahead for good IDNs Brian W. Spolarich
- Re: [idn] Planning ahead for good IDNs Marc Blanchet
- Re: [idn] Planning ahead for good IDNs Brian W. Spolarich
- Re: [idn] Planning ahead for good IDNs John C Klensin
- [idn] RFC2026 - Section 10 Statement J. William Semich
- Re: [idn] RFC2026 - Section 10 S... Paul Hoffman / IMC
- Re: [idn] RFC2026 - Section ... James Seng/Personal
- Re: [idn] RFC2026 - Section 10 S... Jorge Amodio
- Re: [idn] Planning ahead for good IDNs D. J. Bernstein
- Re: [idn] Planning ahead for good IDNs Marc Tamsky
- Re: [idn] Planning ahead for good IDN... J. William Semich
- Re: [idn] Planning ahead for good IDNs William Morris
- Re: [idn] Planning ahead for good IDNs Keith Moore
