From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to opt out of curly-quote spamming altogether? Date: Mon, 24 Aug 2015 19:45:58 +0300 Message-ID: <837fokhby1.fsf@gnu.org> References: <83fv38hfsx.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1440434792 12943 80.91.229.3 (24 Aug 2015 16:46:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 24 Aug 2015 16:46:32 +0000 (UTC) Cc: emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 24 18:46:24 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZTut4-0004R7-7d for ged-emacs-devel@m.gmane.org; Mon, 24 Aug 2015 18:46:22 +0200 Original-Received: from localhost ([::1]:55419 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTut3-00071J-Jj for ged-emacs-devel@m.gmane.org; Mon, 24 Aug 2015 12:46:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48408) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTusy-0006xq-2q for emacs-devel@gnu.org; Mon, 24 Aug 2015 12:46:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZTusu-0004Oe-Mk for emacs-devel@gnu.org; Mon, 24 Aug 2015 12:46:16 -0400 Original-Received: from mtaout24.012.net.il ([80.179.55.180]:60627) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTusu-0004O6-F7 for emacs-devel@gnu.org; Mon, 24 Aug 2015 12:46:12 -0400 Original-Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0NTL00P00I1U7000@mtaout24.012.net.il> for emacs-devel@gnu.org; Mon, 24 Aug 2015 19:38:13 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NTL00H1NI7P0X90@mtaout24.012.net.il>; Mon, 24 Aug 2015 19:38:13 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.180 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:189110 Archived-At: > Date: Mon, 24 Aug 2015 09:34:09 -0700 (PDT) > From: Drew Adams > Cc: emacs-devel@gnu.org > > > > `help-quote-translation' does seem to prevent curly quotes in > > > *Help* buffers, so at least there's that. But I'm looking for > > > a switch to turn this virus OFF everywhere - to return to > > > Classic Emacs. Surely such a simple ON/OFF switch exists? > > > > It doesn't. What you see in Info is literal characters generated > > when the documentation is built during the Emacs build process. > > So, to change that, you will have to regenerate the documentation, > > telling makeinfo not to produce Unicode characters there. > > > > Alternatively, you can set up your standard-display-table to display > > those characters as their ASCII equivalents. > > That's horrible. Users should be able to control this, easily. Why? We don't have easy controls for displaying one character as another. Why should these characters be different? > I don't see this problem in a Windows binary from 2014-11-30. The > regression was apparently introduced to the Windows builds between > then and 2014-12-29. It's the question of which version of Texinfo was used for producing the docs. The defaults in Texinfo changed recently, independently of Emacs development. > A display-table hack would presumably change all uses of a curly > quote. A display table can be specific to a buffer or a window. See the ELisp manual for more about that. But it was you that asked for a switch that changed them _everywhere_, which is why I suggested standard-display-table, which is global. > That's not appropriate - it is only the code-"quoting" > uses that need to be changable/configurable by a user. What is "code-'quoting'"? An Info manual is not code, it's mostly text, but you still wanted these characters changed there.