Re: [idn] URL encoding in html page

["David Leung \(Neteka Inc.\)" <david@neteka.com>]

> > The *real* problem is guaranteeing interoperability for UTF-8, UTF-16,
> > and UTF-32, which are the three sanctioned encoding forms of Unicode
>
> The obvious choice for Internet protocols is UTF-8. See RFC 2277.
> Systems that use 16-bit encodings internally, such as Windows, handle
> UTF-8 conversions at the boundary between the system and the network.
>
> What's the problem?

Totally agree, I thought the IETF has decided on using UTF8 on all protocol.
So I dont understand why someone is saying me trying to predict the future
that all application and protocol should move towards the use of UTF8. It
seems like we(UTF8 supporters) are taking the role of Mark Davis, trying to
promote the use of Unicode : )

David Leung