From: Joerg L. <jo...@us...> - 2003-12-16 16:21:41
|
On 15.12.03, Mark A. Wicks wrote: > On Mon, Dec 15, 2003 at 03:58:12PM -0500, Alvaro Tejero Cantero wrote: > > When using the figures within latex, they look good on the DVI, PS and > > PDF (with PDFLATEX) output, but not with the DVIPDFM output. > > This isn't a bug in dvipdfm per se, but it's a bug in the external > command that dvipdfm uses to convert EPS to PDF for embedded images. I > think the following change will fix your problem. If you can find the > dvipdfm "config" file, try changing the line: > > D "zcat -f %i | gs -q -sPAPERSIZE=a0 -sDEVICE=pdfwrite -dCompatibilityLevel=1.2 -dUseFlateCompression=true -sOutputFile=%o - - > > to > > D "epstopdf --outfile=%o %i" Alternatively, you can replace the -sPAPERSIZE option by -dEPSCrop, which uses the bounding box specified in the EPS file, i.e. D "zcat -f %i | gs -q -dEPSCrop -sDEVICE=pdfwrite -dCompatibilityLevel=1.2 -dUseFlateCompression=true -sOutputFile=%o - - Note that this requires at least Ghostscript 8.0. > BTW, dvipdfm (and pdftex) have a crude internal PostScript interpreter > that works on very restrictive subset of PS files, such as those that > come from MetaPost. I don't know anything about PyX (and I also don't > subscribe to the list), but if there's an option for changing the > "prologues" output (like the MetaPost option) dvipdfm could be made to > read it natively without needing to call an external converter. The Postscript used by PyX is also very small subset of the Postscript language, so in principle a direct interpretation by dvipdfm or pdftex should be possible. Is there a definition of the PS subset implemented by dvipdfm or pdftex? Best regards, Jörg -- JOERG LEHMANN | PyX - High quality PostScript figures with Python & TeX jo...@lu... | Visit http://pyx.sourceforge.net/ |