Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!ptsfa!ihnp4!occrsh!occrsh.ATT.COM!labsms.UUCP!lmm
From: lmm@labsms.UUCP
Newsgroups: comp.text
Subject: Re: devps vs. Transcript
Message-ID: <99600003@labsms.UUCP>
Date: Thu, 15-Oct-87 10:30:00 EDT
Article-I.D.: labsms.99600003
Posted: Thu Oct 15 10:30:00 1987
Date-Received: Sat, 17-Oct-87 20:46:46 EDT
References: <2660@dalcs.UUCP>
Lines: 27
Nf-ID: #R:dalcs.UUCP:-266000:labsms.UUCP:99600003:000:925
Nf-From: labsms.UUCP!lmm    Oct 15 09:30:00 1987


> Has anyone used the devps package from Pipeline Associates
> for interfacing with a postscript printer?  I would
> nappreciate any positive or negative comments, or comparisons with
> Transcript from Adobe.  Devps is considerably less expensive
> than Transcript.


We have both packages on a machine, and use them both,  I like the
'enscript' program that comes with Transcript for printing straigt text
files. (the Devps has a similar program but not as flexible).

When printing troff documents, Devps gives you a lot more capabilities
than what I've been able to do with Transcript.

ie:	downloadable fonts
	inclusion of Macpaint documents
	inclusion of PostScript code in a troff document.
	Fancy macros to do shading, rotation, etc on text.


Summary:

Transcript is better for printing plain text files in various ways.

Devps is better for Troff documents. (If you want to be fancy, otherwise
they both work fine)