[idn] Re: idn-uri

[Martin Duerst <duerst@w3.org>]

Hello Bruce,

Here is the behavior according to RFCs/drafts:

RFC 2396 only: only ASCII in domain name part

IRI draft only: only ASCII in domain name part
(http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-08.txt)

RFC 2396 + idn-uri draft: ASCII and %-escaping (based on UTF-8)
(http://www.ietf.org/internet-drafts/draft-ietf-idn-uri-01.txt)

IRI draft + idn-uri draft: ASCII, %-escaping (based on UTF-8)
and characters encoded based on the encoding of the page

Of course, I hope that browsers (and similar tools) will support
both of my drafts, so that page authors don't have to take care
of this; to some extent, they already do.

If you see any way in which to improve the above drafts so that
you would not have had to ask me, please tell me.

Regards,   Martin.

At 13:04 01/12/10 +0900, Bruce Thomson wrote:
>Martin,
>
>I'd like to ask for a clarification of the idn-uri draft. As I understand
>it, URIs should be able to contain %-escaped UTF-8 characters
>in their domain name portions. So for instance when writing an
>A HREF link in an HTML page, one could specify an idn through
>an escape sequence.
>
>My question is, since most people write HTML using various local
>code pages, do you envision that it would also be possible to write
>a link in HTML using the local encoding? The browser would then
>translate to the appropriate escape sequence before putting
>it on the wire. Or, do you want the HTML author to handle this?