Re: possible single-quote bug in PDF docs (was: trouble with Imenu integration)

[Michael Gilbert <magicgilbert@gmail.com>]

>>>> Following the instructions from manual, I have this near the end of my startup file (I hope that is copied correctly):
>>> 
>>>> 	(add-hook ’org-mode-hook
>>>> 		   (lambda () (imenu-add-to-menubar "Imenu")))
>>> 
>>> Um... Wrong type of quote?  It's
>>> 'org-mode-hook (ASCII 39)
>>> not
>>> ’org-mode-hook (Unicode 8217)
>> 
>> 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...
>> 
>> 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 — the renderer turns all the single quotes into curly quotes, even when they are being used in code.
> 
> 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  <pre>, <code>, <kbd>, or<script>). 

— Michael