Text Formatting ⇒ ** WARNING ** Interpreting PS code failed

[Laurentius]

What do these error messages mean?

** WARNING ** Unknown token "save"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(277.948, 404.797)" (in PDF)
** WARNING ** >> xxx "ps: save /setgray { pop } def"
** WARNING ** >> Reading special command stopped around >>/setgray { pop } def<<
** WARNING ** Unknown token "restore"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(277.948, 404.797)" (in PDF)
** WARNING ** >> xxx "ps: restore"
** WARNING ** Unknown token "save"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(192.578, 349.161)" (in PDF)
** WARNING ** >> xxx "ps: save /setgray { pop } def"
** WARNING ** >> Reading special command stopped around >>/setgray { pop } def<<
** WARNING ** Unknown token "restore"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(192.578, 349.161)" (in PDF)
** WARNING ** >> xxx "ps: restore"
** WARNING ** Unknown token "save"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(363.318, 349.161)" (in PDF)
** WARNING ** >> xxx "ps: save /setgray { pop } def"
** WARNING ** >> Reading special command stopped around >>/setgray { pop } def<<
** WARNING ** Unknown token "restore"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(363.318, 349.161)" (in PDF)
** WARNING ** >> xxx "ps: restore"
** WARNING ** Unknown token "save"
** WARNING ** Interpreting PS code failed!!! Output might be broken!!!
** WARNING ** Interpreting special command ps: (ps:) failed.
** WARNING ** >> at page="1" position="(162.316, 321.079)" (in PDF)

[localghost]

I don't see any errors messages, just warnings. That's an important difference. It would be much more interesting to see the code in form of a minimal example that produces them. And some specific information about the involved typesetting engine would also be helpful.


Thorsten

[Stefan Kottwitz]

This could mean problems regarding conversion from DVI to PDF (using dvipdfmx possible). It could be caused by wrong a driver option. It's hard to say if you don't show the code (at least the preamble) and the way you compile. Perhaps this doesn't match.

Stefan

[Laurentius]

I just found out that this is caused by the qtree package
and the command (f. Ex.):

\Tree [.{ego fateor} [.homines [.{\it attr.} multos [.{(et \ldots\ et \ldots)\\ moderatos, gravis} ] ] [.{\it præd.\\\rm (\ldots\ et \ldots)} [.fuisse [.{animo ac virtute} excellenti ] ] [.exstitisse [.sine doctrina ] [.per {se ipsos} ] [.habitu [.naturae ipsius ] [.divino prope ] ] ] ] ] ]

[Stefan Kottwitz]

I still think more information is required, as I said above, because this code runs without problem for me.

Code: Select all

\documentclass{article}
\usepackage{qtree}
\begin{document}
\Tree [.{ego fateor} [.homines [.{\it attr.} multos [.{(et \ldots\ et \ldots)\\
  moderatos, gravis} ] ] [.{\it præd.\\\rm (\ldots\ et \ldots)} [.fuisse
  [.{animo ac virtute} excellenti ] ] [.exstitisse [.sine doctrina ]
  [.per {se ipsos} ] [.habitu [.naturae ipsius ] [.divino prope ] ] ] ] ] ]
\end{document

tree.png (6.01 KiB) Viewed 8937 times

Stefan

[Dimmy]

Hi!
I am a complete newb, so what I say might make no sense in your case. But anyways. My problem was similar (Unknown token "save" warning with a bunch of other warnings and in my case nothing would show up on the pdf, even though no errors occurred).

I fixed it by setting the following in Configure TeXStudio:
Build&View: DVI->PS->PDF Chain
Default compiler: PDFLaTeX

Actually, I'm not sure what will happen if Build&View is left default. But anyways - maybe this will fix your issues too.