[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: address@hidden: [patch] url-hexify-string does not follow W3C spec]
From: |
Stefan Monnier |
Subject: |
Re: address@hidden: [patch] url-hexify-string does not follow W3C spec] |
Date: |
Mon, 31 Jul 2006 12:08:10 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
> 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
- address@hidden: [patch] url-hexify-string does not follow W3C spec], Richard Stallman, 2006/07/30
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], Thien-Thi Nguyen, 2006/07/30
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], YAMAMOTO Mitsuharu, 2006/07/30
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], Thien-Thi Nguyen, 2006/07/31
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], Jason Rumney, 2006/07/31
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec],
Stefan Monnier <=
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], David Smith, 2006/07/31
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], Thien-Thi Nguyen, 2006/07/31
- Re: address@hidden: [patch] url-hexify-string does not follow W3C spec], YAMAMOTO Mitsuharu, 2006/07/31