From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#16292: 24.3.50; info docs now contain single straight quotes instead of `' Date: Fri, 2 May 2014 12:20:38 -0700 (PDT) Message-ID: <9a37ee13-e1cb-4ac5-8241-85feed5370fb@default> References: <<20131229220810.GF7972@boo.workgroup>> <<52C25D07.80808@cs.ucla.edu>> <<8338l91l2t.fsf@gnu.org>> <<52C4C95C.2010905@cs.ucla.edu>> <<837gajyrq1.fsf@gnu.org>> <<52C4F008.5060003@cs.ucla.edu>> <<83zjnextyg.fsf@gnu.org>> <<52C5BDD1.2050009@cs.ucla.edu>> <<83ppoaxfu6.fsf@gnu.org>> <<52C607DA.3090009@cs.ucla.edu>> <<83fvp5xzk0.fsf@gnu.org>> <<52C6F2C5.10505@cs.ucla.edu>> <<83mwjcx1i9.fsf@gnu.org>> <> <<52C750C4.6040006@cs.ucla.edu>> <> <<8338l4w5pj.fsf@gnu.org>> <> <<83ha9jv5lh.fsf@gnu.org>> <> <<838uuvum9n.fsf@gnu.org>> <> <<8338l2v1tn.fsf@gnu.org>> <<52C9BA68.7050703@cs.ucla.edu>> <<83fvp2tcqx.fsf@gnu.org>> <<52C9BCBF.7050904@cs.ucla.edu>> <<83eh4mtc52.fsf@gnu.org>> <<52C9E53D.8070106@cs.ucla.edu>> <<838uutu5mu.fsf@gnu.org>> <<52CA3FB9.30509@cs.ucla.edu>> <<834n5ht7bz.fsf@gnu.org>> <<52CB5517.4030502@cs.ucla.edu>> <<83lhyssawf.fsf@gnu.org>> <> <<83eh0c11mt.fsf@gnu.org>> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1399058604 5167 80.91.229.3 (2 May 2014 19:23:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 May 2014 19:23:24 +0000 (UTC) Cc: eggert@cs.ucla.edu, grfz@gmx.de, 16292@debbugs.gnu.org To: Eli Zaretskii , Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 02 21:23:17 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1WgJ3E-0003Rx-D8 for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 May 2014 21:23:16 +0200 Original-Received: from localhost ([::1]:46014 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WgJ3D-0002fZ-OQ for geb-bug-gnu-emacs@m.gmane.org; Fri, 02 May 2014 15:23:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34958) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WgJ1D-0007ds-6M for bug-gnu-emacs@gnu.org; Fri, 02 May 2014 15:21:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WgJ14-0002Rz-E7 for bug-gnu-emacs@gnu.org; Fri, 02 May 2014 15:21:11 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:59605) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WgJ14-0002Rn-B4 for bug-gnu-emacs@gnu.org; Fri, 02 May 2014 15:21:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WgJ13-0006Ex-MZ for bug-gnu-emacs@gnu.org; Fri, 02 May 2014 15:21:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 May 2014 19:21:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16292 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 16292-submit@debbugs.gnu.org id=B16292.139905845023957 (code B ref 16292); Fri, 02 May 2014 19:21:01 +0000 Original-Received: (at 16292) by debbugs.gnu.org; 2 May 2014 19:20:50 +0000 Original-Received: from localhost ([127.0.0.1]:48723 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WgJ0r-0006EK-KE for submit@debbugs.gnu.org; Fri, 02 May 2014 15:20:50 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:22072) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WgJ0p-0006E1-57 for 16292@debbugs.gnu.org; Fri, 02 May 2014 15:20:47 -0400 Original-Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s42JKdlK016388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 May 2014 19:20:40 GMT Original-Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s42JKcxL010095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 May 2014 19:20:39 GMT Original-Received: from abhmp0012.oracle.com (abhmp0012.oracle.com [141.146.116.18]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s42JKcsn021836; Fri, 2 May 2014 19:20:38 GMT In-Reply-To: <<83eh0c11mt.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.8 (707110) [OL 12.0.6691.5000 (x86)] X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:88540 Archived-At: > > AFAIK, there is no way, from Emacs Lisp, to know whether an Info > > file has been built to use '...' or `...'. Is that correct? >=20 > Why not? they are just characters. Huh? Yes, they are characters. And how would you determine whether '...' or `...' quoting of names is in effect in a given Info buffer? You might be able to check whether, say, the Emacs manual has '...' or `...' by moving to a particular node where you expect a particular symbol to be quoted (and that you expect to remain present across Emacs versions), and move to that symbol and test the char before it... But that would be an ugly and inefficient workaround, and different manuals might be built using different makeinfo versions etc. I'm asking for a simple check. Maybe a file-local variable or something. > > IIUC, at Info build time there is a setting, @documentencoding, > > that determines this. >=20 > No, these are ASCII characters, so @documentencoding has nothing > to do with it. But the version of makeinfo does: the latest > versions produce '...'. I thought, from this thread, that builds could control whether '...' or `...' gets used. Is that not the case? And I (mistakenly) thought that @documentencoding was involved with that. If '...' is used systematically from now on, starting with some version of makeinfo, then that is indeed bad news. '...' is absolutely inferior to `...', IMHO. > > Request: Could we please have this information transmitted to > > the resulting Info files somehow, so that it could be obtained > > by Lisp code? >=20 > It is already there: > This is ../../info/emacs.info, produced by makeinfo version 4.13 > from ./emacs.texi. > If the version is 5.x, then you should expect '...'. Yes, at the beginning of the file, outside of what is visible in the manual, i.e., in Info mode. I want something simple, evaluable from Info mode. I don't want to have to widen the buffer or change the mode or jump through any other hoops. A function or a variable whose value lets Lisp code know whether `...' or '...' quoting is in effect. > Note that you could also have Unicode characters there. Where is "there"? How does that relate to this quoting? Are you perhaps referring to a possible use of curly quotes for such quoting? That would indeed be bad (from my point of view). > It's a mess. Perhaps we agree, for once, though we might not agree about what the mess is; dunno.