From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: possible single-quote bug in PDF docs (was: trouble with Imenu integration) Date: Fri, 16 Jul 2010 22:33:02 +0200 Message-ID: References: <9707EA08-D22C-4BDF-98E3-CA3A0CFC250C@gilbert.org> <87fwzjmiqe.wl%dmaus@ictsoc.de> <3B9C662E-184F-4280-A06A-ABB931362067@gilbert.org> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=46933 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZrao-00049W-KZ for emacs-orgmode@gnu.org; Fri, 16 Jul 2010 16:33:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OZran-00056C-6T for emacs-orgmode@gnu.org; Fri, 16 Jul 2010 16:33:10 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:35859) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OZram-000563-SS for emacs-orgmode@gnu.org; Fri, 16 Jul 2010 16:33:09 -0400 Received: by ewy28 with SMTP id 28so1011086ewy.0 for ; Fri, 16 Jul 2010 13:33:07 -0700 (PDT) In-Reply-To: <3B9C662E-184F-4280-A06A-ABB931362067@gilbert.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Michael Gilbert Cc: emacs-orgmode Mailinglist On Jul 16, 2010, at 10:21 PM, Michael Gilbert wrote: > On Jul 16,2010, at 10:36 AM, David Maus wrote: > >>> Following the instructions from manual, I have this near the end =20 >>> of my startup file (I hope that is copied correctly): >> >>> (add-hook =92org-mode-hook >>> (lambda () (imenu-add-to-menubar "Imenu"))) >> >> Um... Wrong type of quote? It's >> 'org-mode-hook (ASCII 39) >> not >> =92org-mode-hook (Unicode 8217) > > Yep. When there wasn't an obvious answer, I found the same thing. =20 > Thank you regardless, David. What effect is it that the incorrect =20 > character has on the LISP processing? The error returned was related =20= > the name of the variable... > > Also, I guess this is a possible bug in the documentation: Looks =20 > like the single quote in the PDF version of the manual is Unicode =20 > 8217. (And of course I copied and pasted, to avoid getting anything =20= > wrong when I typed it!) Would that be something worth correcting? I =20= > have this vague notion that I've encountered it elsewhere. The HTML =20= > version of the manual is rendered correctly, but the PDF is not, I =20 > think. A quick scan suggests this =97 the renderer turns all the =20 > single quotes into curly quotes, even when they are being used in =20 > code. Yes. Unfortunately I don't know a way to fix this. - Carsten