Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!ux1.cso.uiuc.edu!timothyg
From: timothyg@ncsa.uiuc.edu (Timothy Gallivan)
Newsgroups: comp.sys.atari.st.tech
Subject: ghostscript, dvips on ST
Keywords: ghostscript, postscript, dvips, tex
Message-ID: <1991Apr15.212445.18348@ux1.cso.uiuc.edu>
Date: 15 Apr 91 21:24:45 GMT
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: Nat'l Ctr for Supercomp App (NCSA) @ University of Illinois
Lines: 32
Originator: timothyg@harriett


Hi,

This is my third attempt to post this info. I'll get it right
one day.

I have a partial port of ghostscript (GNU project's postscript
interpreter) running on the ST. I know of one small bug, but as
soon as I get gdb working, I hope to exterminate it. I currently
have only the HP DeskJet driver working, but I think (hope) it
will be simple to install any of the other drivers distributed
with ghostscript (i.e. epson).

I am soliciting any information (about the atari and ghostscript)
which might help me to write a screen driver for the ST. I am not
very familiar with ST hardware, TOS, GEM, or the ghostscript
device interface, so that is a tall order. Perhaps someone will
volunteer to write it for me (wishful thinking). Is it possible
to have a GEM screen driver for a non-GEM program? Can I hack
one of the MSDOS VGA drivers?

I also have dvips running on the ST. Dvips converts TeX .dvi files
to postscript files. It supports the use of TeX 'special' commands
to include postscript graphics in TeX/LaTeX documents. The
TeX/dvips/ghostscript combination can be very powerful.

I can post these programs (as they are) if anyone is interested and 
is willing to give me instructions for how to post executables.
Thanks,

Tim Gallivan
timothyg@ncsa.uiuc.edu