Re: Example typo in encode-uri and decode-uri

Robert Zimmermann wrote:
> I think the example for encode-uri and decode-uri there is an typo:

You are correct. Both accented e's should be %C3%A9.

Also, the second argument to str:encode-uri() is supposed to be a boolean,
not a string.

Craig or someone, can you update the site?


Also, soon, a new version of str:encode-uri() will be warranted in order
to accommodate RFC 2396bis [1]: the RFC 2396 successor which is nearing 
completion. The differences that affect the encode-uri function are:

old "unreserved" set: ASCII alphanumerics and -_.!~*'()
new "unreserved" set: ASCII alphanumerics and -_.~
(these are the characters that are always safe to leave untouched)

old "reserved" set: ;/?:@&=+$,[]
new "reserved" set: ;/?:@&=+$,[]#!'()*
(these are the characters that are escaped if the second argument is true).

[1] http://www.gbiv.com/protocols/uri/rev-2002/rfc2396bis.html