[OS X TeX] Fonts and PSNFSS

Alain Schremmer Schremmer.Alain at verizon.net
Sun Jun 13 04:51:34 CEST 2004

I am so obsessed with this thing that I will take up your time and respond.

(1) The sw issue. I am not going to do anything about it. You have 
instilled the fear of the Godesses in me.

(2) The person who gave me the file had also given me a pdf which I now 
realize is what I had seen and misled me into thinking that /I /had 
typeset it.

(a) I searched for dvips and found

    \usepackage[colorlinks=true,linkcolor=red, pdftitle={linear algebra
    book}, pdfauthor={david santos},  bookmarksopen, _dvips]{hyperref_}

where the underline came from the Find Panel.

(b) I changed the TeXshop Typesetting preference to TeX + Ghostscript 
and got

    ! Undefined control sequence.
    <argument> ...\string \color @white\endcsname \@@
    l.41 \psset at bordercolor{white}

However, I got that as a /copy/. Before I selected it it was the same

       !Undefined control sequence <recently read> \c at lor@to at ps
       1.41 \psset at bordercolor(white)

as before. (I don't understand why the console reacts to selection.)

(c) I replaced dvips by pdftex one at a time with the same as in (b) 
except it did not like pdftexnames.
 Then I replaced dvips by pdftex in the first two and erased dvipsnames 
in the third with the same except that the line


had disappeared.

(d) Find Panel found no occurrence of [textures], [truetex] or [vtex], 

(e) pstricks is there all right.

Well, as I said, at this point it is really only an obsession so, again, 
leave it alone or else I will get back to you.

Very gratefully,

P.S. I got your 4.35 PM about an hour later than your 4.49 PM about 
which I have not yet done anything. (I am trying to get ahead in my book)

Bruno Voisin wrote:

> Well, that's not an easy one to debug, unless you've got some 
> experience with LaTeX already! LaTeX's error message are often 
> unhelpful, as they point to a line where the error becomes blatant, 
> even if the error was actually created by another instruction several 
> lines earlier.
> I think the most likely cause for what you experienced is that you 
> compiled in pdfTeX mode a document that included the line:
> \usepackage[dvips]{graphics}
> or
> \usepackage[dvips]{color}
> or has a [dvips] option somewhere (or an option corresponding to 
> another driver than [pdftex], like [textures], [truetex] or [vtex]).
> How to debug this: I used BBEdit to do a multifile search for 
> "c at lor@to at ps" over the whole directory 
> /Library/teTeX/share/texmf.tetex/tex/latex/, it returned the name of 
> several files inside 
> /Library/teTeX/share/texmf.tetex/tex/latex/graphics/, including in 
> particular dvips.def, textures.def, etc.
> It may also be that your document uses the changebar package, and that 
> this package uses the option [dvips] by default. Or that it uses the 
> pstricks package, since searching for "psset at bordercolor" returns only 
> the file 
> /Library/teTeX/share/texmf.tetex/tex/latex/graphics/pstcol.sty which 
> is said to provide "PSTricks color colompatibility".
> How to solve the problem: replace the [dvips] option by [pdftex], or 
> simply erases it (I think TeXShop has a way of figuring out by itself 
> which option to use), or typeset in TeX + Ghostscript mode instead of 
> pdfTeX. In case your document uses the pstricks package, then the TeX 
> + GhostScript mode is the only solution.
> Generally if the error message mentions a command with "ps" in its 
> name, it's reasonable to try the TeX + Ghostscript mode and see 
> whether it cures things.
> [...]

> Bruno Voisin
> -----------------------------------------------------
> Post: <mailto:MacOSX-TeX at email.esm.psu.edu>
> Please see <http://www.esm.psu.edu/mac-tex/> for list
> guidelines, information, and LaTeX/TeX resources.
Post: <mailto:MacOSX-TeX at email.esm.psu.edu>
Please see <http://www.esm.psu.edu/mac-tex/> for list
guidelines, information, and LaTeX/TeX resources.

More information about the macostex-archives mailing list