From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "David Smith" Newsgroups: gmane.emacs.devel Subject: Re: [davidsmith@acm.org: [patch] url-hexify-string does not follow W3C spec] Date: Tue, 01 Aug 2006 01:35:12 +0900 Message-ID: <87lkq9ivgf.fsf@acm.org> References: <44CDDF7A.8060404@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0398419431==" X-Trace: sea.gmane.org 1154364320 6161 80.91.229.2 (31 Jul 2006 16:45:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 31 Jul 2006 16:45:20 +0000 (UTC) Cc: Thien-Thi Nguyen , emacs-devel@gnu.org, YAMAMOTO Mitsuharu , Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 31 18:45:14 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 1G7asn-0006Ad-Ot for ged-emacs-devel@m.gmane.org; Mon, 31 Jul 2006 18:44:46 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7asm-0007VT-P1 for ged-emacs-devel@m.gmane.org; Mon, 31 Jul 2006 12:44:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G7ajw-00076E-Nn for emacs-devel@gnu.org; Mon, 31 Jul 2006 12:35:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G7ajv-00073P-8E for emacs-devel@gnu.org; Mon, 31 Jul 2006 12:35:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7ajv-00073D-46 for emacs-devel@gnu.org; Mon, 31 Jul 2006 12:35:35 -0400 Original-Received: from [66.111.4.26] (helo=out2.smtp.messagingengine.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G7amV-0002CK-7d; Mon, 31 Jul 2006 12:38:15 -0400 Original-Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id AF17AD92A97; Mon, 31 Jul 2006 12:35:25 -0400 (EDT) Original-Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by frontend3.internal (MEProxy); Mon, 31 Jul 2006 12:35:29 -0400 X-Sasl-enc: 45z5UNx4zfel0UnK3mAHZ5hIcOjYHHdigmKZuDS5mwxm 1154363729 Original-Received: from exponent (p8076-ipad507marunouchi.tokyo.ocn.ne.jp [222.148.87.76]) by mail.messagingengine.com (Postfix) with ESMTP id E9AC8433F; Mon, 31 Jul 2006 12:35:27 -0400 (EDT) Original-Received: from dds by exponent with local (Exim 4.50) id 1G7ajd-0007xE-Tt; Tue, 01 Aug 2006 01:35:17 +0900 Original-To: Stefan Monnier In-Reply-To: (Stefan Monnier's message of "Mon, 31 Jul 2006 12:08:10 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.0 (gnu/linux) X-Mailman-Approved-At: Mon, 31 Jul 2006 12:44:27 -0400 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:57849 Archived-At: --===============0398419431== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable Stefan Monnier writes: >> Alternatively, we could add an optional arg ENCODING, for specifying an >> encoding other than utf-8. That might be a cleaner interface than requir= ing >> the user to make the string unibyte before passing it to url-hexify-stri= ng. > > 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 t= han > utf-8 (rare and getting rarer in the future, most likely) is really not > a big deal. > > So far, this suggestion does seem to satisfy all issues. Nguyen, is this as easy to implement as it sounds? Yamamoto-san, your issue is valid and this is what you suggested originally, right? =2D-=20 David D. Smith --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEzjFFEJGOueZRHH4RAlVbAJ9cBvgfu+W60xZQ4mx7kEvanoC1jQCgpDeI fUOkNhGS/ZiOugwJuv04vUI= =kCls -----END PGP SIGNATURE----- --=-=-=-- --===============0398419431== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --===============0398419431==--