🚀 go-pugleaf

In article <11030@phoenix.Princeton.EDU> vlo@taipei.Princeton.EDU (John Vlontzos) writes:
| I hope problems like this will be solved once and for all someday.
| Ok. here is the problem:
| 
| I got dvips40 working for plain text files. However, there are
| some incompatibilities with psfig.
| The first is simple to fix. Psfig puts postscript text into the 
| file using a \special{pstext= ..} while dvips expects \special{" ...}
| I changed that in  psfig.tex
| 
You are not using the right \specials from psfig. The psfig distribution
includes three (3) \specials sets for using different dvi(x)ps drivers.
Differences are in \special format. dvips4.x recognizes 
        \special{psfile="filename"}
        \special{psfile="filename"[ key=value]*}
        \special{ps: <ps text>}
        \special{ps:: <text>}
        \special{ps::[begin] <ps text>}
        \special{ps::[end] <ps text>}
        \special{ps: plotfile <ps file>}
	\special{" text}
	\special{! text}

| The second is that it simply refuses to print figures. I keep
| getting a diagnostic "nocurrentpoint offending command currentpoint".
| It is clear that the problem is somewhere in the startTeXfig definition
| dvips uses. Before I fixed problem one (above) the figure would be printed
| but in the wrong position. After I fixed it, I get the above diagnostic
| (by the way I'm using lprep68.pro with the command
| "dvips -h lprep68.pro file", printing on an imagen with ultrascript)
| 
| Can anybody help??
| 
Maybe a following of the previous error. We used dvips/psfig, with mac
files, and we have no trouble.

| Thanks in advance
| John Vlontzos
| Princeton


| Bertrand DECOUTY             | EMAIL : decouty@irisa.fr, decouty@irisa.uucp  |
| IRISA - INRIA                |         {uunet,mcvax,inria}!irisa!decouty     |
| Campus de Beaulieu           | PHONE : +33  99 36 20 00                      |
| F-35042 Rennes Cedex - FRANCE| FAX : +33  99 38 38 32 | TELEX: 950473 UNIRISA|