James Seng wrote: >>Then, you should not convert ACE-form iDN int UTF8 and render it for >> >> >users. > > >>Doesn't this Looks absurd ? You claims seem against IDNA drafts. >>My current argument is based on IDNA draft section 6. >> >> > >Section 6.1 describe how "Entry and display in application". It makes no >mention of UTF-8 as can read. Which paragraph are you referring to? > > Look into Section 6.1 and the IDNA architecture figure, please. The authors themselves may clarifiy the reading of the section, better than you James and me.
============================ 6.1 Entry and display in applications (snip) In protocols and document formats that define how to handle specification or negotiation of charsets, labels can be encoded in any charset allowed by the protocol or document format. If a protocol or document format only allows one charset, the labels MUST be given in that charset. In any place where a protocol or document format allows transmission of the characters in internationalized labels, internationalized labels SHOULD be transmitted using whatever character encoding and escape mechanism that the protocol or document format uses at that place
