Re: [davidsmith@acm.org: [patch] url-hexify-string does not follow W3C spec]

[Stefan Monnier <monnier@iro.umontreal.ca>]

> Alternatively, we could add an optional arg ENCODING, for specifying an
> encoding other than utf-8. That might be a cleaner interface than requiring
> the user to make the string unibyte before passing it to url-hexify-string.

I'd rather not add any arg and simply encode with utf-8 if it's not
already unibyte.  After all, non-utf-8 uses should be inexistent right now
since the code signals an error, and requiring an explicit call to
encode-coding-string for those rare cases where you want something else than
utf-8 (rare and getting rarer in the future, most likely) is really not
a big deal.


        Stefan