Typophile - Importing potrace/ghostscript eps files into Fontlab - Comments

I know a guy who wrote a

twardoch — Tue, 12 Feb 2008 11:12:33 -0800

I know a guy who wrote a citation management database in PostScript :)

Awesome. Thanks, Adam.

Christian Robertson — Tue, 12 Feb 2008 09:09:08 -0800

Awesome. Thanks, Adam. It’s nuts how Ghostscript uses ps to translate ps.

BTW, we would love to

twardoch — Tue, 12 Feb 2008 03:56:29 -0800

BTW, we would love to integrate Ghostscript as a library in FontLab products, which would allow us to import pretty much any PostScript, EPS and PDF files, but unfortunately, their licensing terms are quite prohibitive.

Christian, gs -q

twardoch — Tue, 12 Feb 2008 03:49:55 -0800

Christian,

gs -q -dNODISPLAY -dNOPAUSE -dSAFER ps2ai.ps a_a.eps > a_a_new.eps

should do the trick.

Adam

This is unpopular, but

DanGayle — Mon, 11 Feb 2008 23:56:28 -0800

This is unpopular, but potrace is available from within the Fontforge environment, from the command line. Michael Boyer might be the best person to ask about that, as he seems very open to helping out with that sort of thing.

Explained a little here

Importing potrace/ghostscript eps files into Fontlab

Christian Robertson — Mon, 11 Feb 2008 21:11:17 -0800

I’ve been trying to import eps files output from potrace and/or ghostscript into Fontlab with no success. Can anyone think of an automated way (as in accessible via script) to make this work without having to write a an eps interpreter or worse, a script for Illustrator?

Just in case any Postscript hackers are reading this, I’m attaching the output from potrace. If there is a simple thing in the output that is offending Fontlab, I wouldn’t mind parsing the eps to strip it out.