[OS X TeX] Distiller
siepo at cybercomm.nl
Sun Jan 29 11:04:25 EST 2006
On Sun, Jan 29, 2006 at 03:34:24PM +0000, Jonathan Kew wrote:
> On 29 Jan 2006, at 2:14 pm, Siep Kroonenberg wrote:
> >I believe it is robust for valid eps files, since the boundingbox
> >comments should occur in the header or in the trailer. For a valid
> >eps file, these will be the only parts that will get scanned.
> OK, that sounds more hopeful... your original phrase "parse all
> resulting strings" sounded rather global in its scope.
> If you're splitting the entire EPS file on /\r?\n|\n/ into an array
> of lines (even if you only examine the lines from the header and
> trailer), you'll need to take care to restore the exact original line
> separator in each place when outputting the file. Some of the line-
> breaks found might actually be part of binary data in the body of the
> file. In that case, allowing the tool to "regularize" them all to \n,
> for example, will be destructive.
Both the Ruby and the Perl versions of split have options to save
the separators along with the separatees.
But for conversion to pdf it may not be necessary to rewrite the
original file: just feed Ghostscript a file with code which defines
page size and translating the eps to a (0,0) origin, then the
original file, and then a `-c grestore' keyword.
------------------------- Info --------------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
& FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Archive: http://tug.org/pipermail/macostex-archives/
More information about the MacOSX-TeX