From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [davidsmith@acm.org: [patch] url-hexify-string does not follow W3C spec] Date: Mon, 31 Jul 2006 12:08:10 -0400 Message-ID: References: <44CDDF7A.8060404@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1154362213 31026 80.91.229.2 (31 Jul 2006 16:10:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 31 Jul 2006 16:10:13 +0000 (UTC) Cc: davidsmith@acm.org, Thien-Thi Nguyen , YAMAMOTO Mitsuharu , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 31 18:10:09 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G7aL6-0007yS-W2 for ged-emacs-devel@m.gmane.org; Mon, 31 Jul 2006 18:09:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7aL6-0001Ro-Bk for ged-emacs-devel@m.gmane.org; Mon, 31 Jul 2006 12:09:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G7aJX-0000Wx-V2 for emacs-devel@gnu.org; Mon, 31 Jul 2006 12:08:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G7aJU-0000Uv-4t for emacs-devel@gnu.org; Mon, 31 Jul 2006 12:08:19 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7aJT-0000Um-Ly for emacs-devel@gnu.org; Mon, 31 Jul 2006 12:08:15 -0400 Original-Received: from [209.226.175.4] (helo=tomts16-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G7aM6-0007qz-Mk; Mon, 31 Jul 2006 12:10:58 -0400 Original-Received: from localhost ([70.55.140.127]) by tomts16-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060731160810.XBPM27612.tomts16-srv.bellnexxia.net@localhost>; Mon, 31 Jul 2006 12:08:10 -0400 Original-Received: by localhost (Postfix, from userid 20848) id 909278883; Mon, 31 Jul 2006 12:08:10 -0400 (EDT) Original-To: Jason Rumney In-Reply-To: <44CDDF7A.8060404@gnu.org> (Jason Rumney's message of "Mon, 31 Jul 2006 11:46:18 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:57846 Archived-At: > 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