From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: with-url Date: Sat, 21 Jan 2017 17:54:35 +0200 Message-ID: <83lgu45ryc.fsf@gnu.org> References: <87mvffva75.fsf@gnus.org> <8360m2vhze.fsf@gnu.org> <87mvfeg0ck.fsf@gnus.org> <87inq2g046.fsf@gnus.org> <83wpeiu0y5.fsf@gnu.org> <87shocbf9y.fsf@gnus.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1485014099 16635 195.159.176.226 (21 Jan 2017 15:54:59 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 21 Jan 2017 15:54:59 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 21 16:54:50 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUy09-0003ON-TH for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2017 16:54:50 +0100 Original-Received: from localhost ([::1]:60534 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUy0D-0003TO-31 for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2017 10:54:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40301) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUy03-0003TH-UH for emacs-devel@gnu.org; Sat, 21 Jan 2017 10:54:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUy00-0004Db-2u for emacs-devel@gnu.org; Sat, 21 Jan 2017 10:54:43 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:60554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUxzz-0004DU-Vk; Sat, 21 Jan 2017 10:54:40 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2375 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cUxzz-0006Hx-9D; Sat, 21 Jan 2017 10:54:39 -0500 In-reply-to: <87shocbf9y.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 21 Jan 2017 16:31:53 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211463 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Sat, 21 Jan 2017 16:31:53 +0100 > > Eli Zaretskii writes: > > >> (But in a networking environment, the Emacs terminology is very > >> confusing. You have `coding system' where all standards say `charset', > >> and in addition you have all the standards talking about `encoding', > >> which is things like base64 and url-encoding. So the parameter list, if > >> changed, will talk about :data-coding-system and > >> :data-transfer-encoding, which is probably not as helpful as it should > >> be. > > > > How about :coding-system and :transfer-encoding instead? > > Thinking about it a bit more, I'm reverting the working to "charset" > again. That's what this is about, since the string in question will end > up in a HTTP header saying charset="foo". Once again, may I suggest mime-charset instead? We already use this elsewhere in Emacs, and using it here will prevent confusion with Emacs charsets. > Emacs coding systems are (vaguely) supersets of the charset concept No, they aren't.