[OS X TeX] Problem with Quotes in PDF File

[Maarten Sneep]

On 28 Jan 2006, at 22:56, Rick Zaccone wrote:

> On Jan 28, 2006, at 4:06 PM, Alan Munn wrote:
>
>>> There are two differences.  In the source file the left quote is  
>>> octal 047 (39 decimal, 0x27 hex).  In the PDF file the left quote  
>>> is 0222 in octal (146 decimal, 0x92 hex).  It seems that the  
>>> character has been translated into its "curly" equivalent.  The  
>>> same thing has happened to the right quote.
>>
>> \usepackage{upquote} does what you want, I think.
>
> This does indeed fix my problem!  It works with the fancyvrb  
> package too.  Thanks so much.

So, there are options. Good. Now here is a harder one (at least I  
think it is harder).

I am rewriting my BBEdit & TextWrangler TeX integration scripts, and  
for various reasons** I'm using the noweb system***. Now the  
combination of AppleScript and noweb is one which can be funny. noweb  
pretty much assumes you use ASCII alone, and sets all code fragments  
in a verbatim-like environment. AppleScript assumes either MacRoman  
or UTF-8. You know this has all the ingredients for an epic clash.

I can avoid most characters in MacRoman that are not in ASCII. There  
is one I have to use: the line continuation character for AppleScript: ¬

When setting the noweb source as MacRoman and telling LaTeX about  
that with \usepackage[applemac]{inputenc}, I can forget about  
typesetting the result, as ¬ in verbatim gives a math-mode clash. If  
I don't specify any encoding, I just get  in the output pdf. The  
resulting script gets the ¬ character that is needed for compilation,  
so all is fine, except for printing. I've tried several combinations,  
but the mathmode within verbatim is the deal killer so far.

It is a pretty low priority problem for me, as it is just the output  
that looks funny, but otherwise it is completely serviceable. If it  
is helpful: I'd like to use the Lucida fonts, perhaps it has some  
exotic font encoding with ¬ in hte right location.

Maarten

* No they are not ready yet, and will not be for some time to come.  
Yes, I will start a CVS for it at some time in the (near) future.
** One is that in these sources I can easily change the name of the  
editor and produce compiled output for both BBEdit and TextWrangler.
*** Noweb is available from http://www.eecs.harvard.edu/~nr/noweb/

------------------------- Info --------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
          & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/