From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Gilbert Subject: Re: possible single-quote bug in PDF docs (was: trouble with Imenu integration) Date: Fri, 16 Jul 2010 15:21:22 -0700 Message-ID: <3C4C24C7-732F-4F0C-BA58-11F8158DE3E5@gmail.com> 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 v1081) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=43668 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZtHv-00005I-Ut for emacs-orgmode@gnu.org; Fri, 16 Jul 2010 18:21:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OZtHu-0002bR-Pa for emacs-orgmode@gnu.org; Fri, 16 Jul 2010 18:21:47 -0400 Received: from mail-pv0-f169.google.com ([74.125.83.169]:59677) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OZtHu-0002bK-Kx for emacs-orgmode@gnu.org; Fri, 16 Jul 2010 18:21:46 -0400 Received: by pvc30 with SMTP id 30so2198486pvc.0 for ; Fri, 16 Jul 2010 15:21:45 -0700 (PDT) In-Reply-To: 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: emacs-orgmode Mailinglist >>>> Following the instructions from manual, I have this near the end of = my startup file (I hope that is copied correctly): >>>=20 >>>> (add-hook =92org-mode-hook >>>> (lambda () (imenu-add-to-menubar "Imenu"))) >>>=20 >>> Um... Wrong type of quote? It's >>> 'org-mode-hook (ASCII 39) >>> not >>> =92org-mode-hook (Unicode 8217) >>=20 >> Yep. When there wasn't an obvious answer, I found the same thing. = Thank you regardless, David. What effect is it that the incorrect = character has on the LISP processing? The error returned was related the = name of the variable... >>=20 >> Also, I guess this is a possible bug in the documentation: Looks like = the single quote in the PDF version of the manual is Unicode 8217. (And = of course I copied and pasted, to avoid getting anything wrong when I = typed it!) Would that be something worth correcting? I have this vague = notion that I've encountered it elsewhere. The HTML version of the = manual is rendered correctly, but the PDF is not, I think. A quick scan = suggests this =97 the renderer turns all the single quotes into curly = quotes, even when they are being used in code. >=20 > Yes. Unfortunately I don't know a way to fix this. I am ignorant of LATEX and your particular architectural challenges of = course. But the way scripts like John Grubers SmartyPants does it is by = only converting those quote marks that are outside of tags indicating = that the section is code or other exempt section (in HTML these would be = 
, , , or