Re: [tlug] Re: Japanese in URLs?

["Nguyen Vu Hung" <vuhung16plus+shape@example.com>]

2008/2/7, Stephen J. Turnbull <stephen@example.com>:
> Jim Breen writes:
>
>  > It would indeed be nice to get Japanese, etc, in URIs or IRIs displaying
>  > correctly, but there is no way a browser can be sure of the coding used.
>
> True at present, AFAIK.  In theory there could be an HTTP header
> specifying the URL's encoding.  There isn't one in RFC 2616, but I
> didn't check for anything more recent.

RFC 2612 ( May 1999 ) is outdated by RFC 2817( May 2000 ) and 2817 is
the latest.

2817 contains no information about URI encoding so 2612 may be
considered the latest.

The problem with this RFC is that it is too old ( 1999 ), it doesn't
support multi-byte ( or noone think of it ? ) and that's why the ugly
%heck-heck is there.

We can either do the URL encoding conversion at client-side, or server
side, or both.
This can be done ( technically ) in couple of ways[1] and the rest of
the world[2] will be happy :D

[1] IMO something like mbase64 is cool.
[2] Spammers, Russian, Japanese, OP and myself.


-- 
Best Regards,
Nguyen Hung Vu ( Nguyễn Vũ Hưng )
vuhung16plus{remove}@example.com
An inquisitive look at Harajuku
http://www.flickr.com/photos/vuhung/sets/72157600109218238/