[OS X TeX] Different versions of epstopdf in mactex re rest of the world?

Daniel Becker daniel.becker at uni-rostock.de
Sun Apr 29 18:39:14 EDT 2007

... I cc to Jürgen Bausa (maintainer? of the c version of epstopdf)  
as he might be interested?

Am 29.04.2007 um 23:53 schrieb Peter Dyballa:

> Am 29.04.2007 um 16:35 schrieb Peter Dyballa:
>>> /usr/local/texlive/2007/bin/i386-darwin/epstopdf
>>> /usr/local/texlive/2007/bin/powerpc-darwin/epstopdf
>> Both of the files are probably identical, only one of them gets  
>> used, depending on the CPU in your mac. Rename the file to <file  
>> name>.pl and remember to invoke it as epstopdf.pl! The binary from  
>> C code will have the name epstopdf.
>> The third file is an elder 'backup' or relict from some other  
>> package that's obviously not up-to-date. Leave it!
>>> /usr/local/texlive/2007/texmf/scripts/tetex/epstopdf.pl
> This third file is actually the newest one! It is version 2.9.6sw  
> from 2007-01-24 and one year younger then the version 2.9.5gw  
> without the .pl file name extension. The actual difference is that  
> quotes have been changed to make the script work also in MS Windows.
> I also looked into epstopdf.sty. Towards the end there is the line:
> 	\@namedef{Gin at rule@.eps}#1{{pdf}{.pdf}{`epstopdf #1}}
> This one offers to put a personal copy of epstopdf.sty into one's  
> private texmf tree and to adjust the name of the epstopdf  
> executable. And a different option is to put the compiled C file  
> into one's ~/bin folder. This directory usually comes quite early,  
> so an epstopdf executable in ~/bin would be preferred over the  
> executable of the same name in /usr/local/texlive/2007/bin/{i386| 
> powerpc}-darwin or /usr/texbin. I think this option should be  
> preferred, before renaming the original epstopdf, because an  
> upgrade of the TeX executables would re-install the Perl script and  
> therefore overwrite the compiled version. And because these updates  
> happened in teTeX and gwTeX by completely removing the /usr/local/ 
> {gw|te}TeX/bin trees, changing the name of the compiled epstopdf  
> does not save it. It should be placed outside the /usr/local/{gw|te} 
> TeX/bin or /usr/local/texlive trees, in /usr/local/bin for system- 
> wide access, or ~/bin for personal use.

ok - so what I did was not the best way to go. To change the line in  
epstopdfsty and have my own copy in my personal tree, that part is ok.

testing the compiled c executable that is now simply epstopdf:

with (in epstopdf.sty)

\@namedef{Gin at rule@.eps}#1{{pdf}{.pdf}{`epstopdf.pl --debug #1}}

I get in my Texshop-console:

) [136] [137 <../../Bilder/C5_1_BarMitKi_A2.pdf> <../../Bilder/ 
altneu.pdf>]* Input filename: ../../Bilder/C5_3_BarMitKi_Z_altneu.eps
* BoundingBox comment: %%BoundingBox:
* Output filename: ../../Bilder/C5_3_BarMitKi_Z_altneu.pdf
* Ghostscript command: gs
* Compression: on
* Ghostscript pipe: gs -q -sDEVICE=pdfwrite  -dAutoRotatePages=/None - 
sOutputFile='../../Bilder/C5_3_BarMitKi_Z_altneu.pdf' - -c quit
* The first eol character was a CR (23) and not immediately followed  
by a LF (-1)
* Scanning header for BoundingBox
* Old BoundingBox: 0 0 504 288
* New BoundingBox: 0 0 504 288
* Offset: 0 0
* Ready.

when using

\@namedef{Gin at rule@.eps}#1{{pdf}{.pdf}{`epstopdf --gsopt=- 
dCompatibilityLevel=1.3 --debug #1}}

I get in my Texshop-console:

[19 <../../Bilder/A1_Z_faksfein.pdf>]This is epstopdf in C 2.2.20
checking temporary filename >>../../Bilder/A3.eps.0.tmp<<
checking temporary filename >>../../Bilder/A3.eps.1.tmp<<
checking temporary filename >>../../Bilder/A3.eps.2.tmp<<
Converting ../../Bilder/A3.eps to ../../Bilder/A3.pdf .....
Adding correct pagesize to EPS ... searching for %%BoundingBox: ...
BoundingBox: 0.000000 0.000000 504.000000 288.000000
(177x101 mm) ...  newline is LF ...  (600 dpi) ... running  
ghostscript ...
gs -q -dNOPAUSE -dBATCH -dUseFlateCompression=true  -sDEVICE=pdfwrite  
-r600  -dCompatibilityLevel=1.3 -sOutputFile=../../Bilder/A3.pdf - 
f ../../Bilder/A3.eps.2.tmp
keeping temporary file >>../../Bilder/A3.eps.2.tmp<<

and a lot of temporary files.

Good is: I can now use ghostscript-options like  - 
Bad: The temporary files & also the final image in my pdf produced by  
pdflatex looks a bit worse than before.

Will try to find out more.....


------------------------- Helpful Info -------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
List Reminders & Etiquette: http://www.esm.psu.edu/mac-tex/list/

More information about the MacOSX-TeX mailing list