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 18:40:05 +0200 Message-ID: <83inp85pui.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> <83lgu45ryc.fsf@gnu.org> <8737gcbchm.fsf@gnus.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1485016896 13910 195.159.176.226 (21 Jan 2017 16:41:36 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 21 Jan 2017 16:41:36 +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 17:41:27 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 1cUyj0-0001Q7-Ou for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2017 17:41:10 +0100 Original-Received: from localhost ([::1]:60670 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUyj5-0007mc-Ox for ged-emacs-devel@m.gmane.org; Sat, 21 Jan 2017 11:41:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUyiC-0007KQ-VA for emacs-devel@gnu.org; Sat, 21 Jan 2017 11:40:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUyi7-0008KM-Ob for emacs-devel@gnu.org; Sat, 21 Jan 2017 11:40:21 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32835) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUyi7-0008KE-Lf; Sat, 21 Jan 2017 11:40:15 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2412 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cUyi6-0000i0-GB; Sat, 21 Jan 2017 11:40:15 -0500 In-reply-to: <8737gcbchm.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 21 Jan 2017 17:32:05 +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:211468 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Sat, 21 Jan 2017 17:32:05 +0100 > > Eli Zaretskii writes: > > > 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. > > The charsets in MIME are the same as the charsets in all other relevant > RFC. It is clear to somebody talking HTTP what a charset is, even if > that person has never heard of MIME. I want to cater to Emacs users and developers as well, and I think mime-charset is a good compromise. Once again, we have a :mime-charset property of coding systems, so using that terminology will I think provide good mnemonic hints both to protocol experts and to Emacs developers.