Re: character set in URIs for drag and drop

[Alex Larsson <alexl redhat com>]

On Fri, 24 Aug 2001, Daniel Veillard wrote:

>   That time it's not in RFC 2396, too old, maybe it has bee superseeded
>   http://www.faqs.org/rfcs/rfc2396.html
>   2.1 URI and non-ASCII characters

Yeah, read that.

>   However each time I have discussed with people from the I18N
> group at W3C I was told that the URI should first be converted to
> UTF8, then the normalization would ocur. There is some recent
> prose on this issue in the XPointer specification:
> 
>    http://www.w3.org/TR/xptr#uri-escaping
> 
> ---------------------
>    1.  Each disallowed character is converted to UTF-8 [IETF RFC 2279]
>        as one or more bytes.
>    2.  Any bytes corresponding to a disallowed character are escaped
>        with the URI escaping mechanism (that is, converted to %HH,
>        where HH is the hexadecimal notation of the byte value).
>    3.  The original character is replaced by the resulting character sequence.
> ---------------------
> 
>   This part had really a lot of review, I would trust it.

This is what I'm doing.

/ Alex