From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: with-url Date: Thu, 29 Dec 2016 19:52:18 +0100 Message-ID: <8760m2ftzx.fsf@gnus.org> References: <87mvffva75.fsf@gnus.org> <8360m2vhze.fsf@gnu.org> <87mvfeg0ck.fsf@gnus.org> <87inq2g046.fsf@gnus.org> <83wpeiu0y5.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1483037566 918 195.159.176.226 (29 Dec 2016 18:52:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 29 Dec 2016 18:52:46 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 29 19:52:38 2016 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 1cMfoZ-0007Ww-Rr for ged-emacs-devel@m.gmane.org; Thu, 29 Dec 2016 19:52:35 +0100 Original-Received: from localhost ([::1]:36938 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMfoe-0004kf-OL for ged-emacs-devel@m.gmane.org; Thu, 29 Dec 2016 13:52:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMfoV-0004jB-16 for emacs-devel@gnu.org; Thu, 29 Dec 2016 13:52:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cMfoR-0004JE-SE for emacs-devel@gnu.org; Thu, 29 Dec 2016 13:52:31 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:58618) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cMfoR-0004J0-M4; Thu, 29 Dec 2016 13:52:27 -0500 Original-Received: from 2.150.52.94.tmi.telenormobil.no ([2.150.52.94] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cMfoO-0001Mk-4p; Thu, 29 Dec 2016 19:52:26 +0100 In-Reply-To: <83wpeiu0y5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Dec 2016 18:58:26 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 80.91.224.195 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:210970 Archived-At: 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? It's the coding system for the data, not the rest of what's transferred, so you need the `data' in there... The headers are each encoded according to various other conventions (the Host is punycode, the User-Agent is ... er... I haven't looked up the standard, but I'm guessing url-encode). > I think this eventually boils down to the question whether most users > of this feature feel more at home with network-style "charset" or with > Emacs-style "coding-system". I don't know the answer. I think calling the parameters :data-coding-system (etc) and then clarifying in the doc string that it's the charset (if you squint at it) is OK... I was just kinda digressing: I think the nomenclature `coding-system' in Emacs is unfortunate, but it's what we're stuck with. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no