Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!LOVELACE.ALBANY.EDU!narten
From: narten@LOVELACE.ALBANY.EDU (Thomas Narten)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Comment on RFC1124 (?)
Message-ID: <8909281341.AA24308@lovelace.albany.edu>
Date: 28 Sep 89 13:41:50 GMT
References: <8909272331.AA28023@asylum.sf.ca.us>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15

One problem with postscript format documents that I have run into is
that not all printers are 100% postscript compatable.  This is perhaps
an unavoidable situation, because my impression is that 100%
compatable postscript printers are somewhat (though perhaps not much)
more expensive than others because of licensing fees.  Persons paying
for printers may not be aware that 100% compatability is an issue.

I'm very much in favor of postscript documents, but worry that 100%
postscript printers aren't as prevalent is they should be.  Can anyone
suggest a solution to this problem?  Is it realistic to put together a
subset of common postscript commands with an eye on avoiding less
common constructs?  Is there software that massages postcript input to
remove uncommon constructs?

Thomas Narten