Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!cnh5730
From: cnh5730@maraba.tamu.edu (Charles Herrick)
Newsgroups: comp.sys.next
Subject: Re: Generating Postscript files.
Message-ID: <CNH5730.91May15163539@maraba.tamu.edu>
Date: 15 May 91 21:35:39 GMT
References: <99Us02Ia07KJ01@JUTS.ccc.amdahl.com>
Sender: usenet@helios.TAMU.EDU
Distribution: na
Organization: Human Race
Lines: 39
In-reply-to: kls30@duts.ccc.amdahl.com's message of 15 May 91 15:54:28 GMT

In article <99Us02Ia07KJ01@JUTS.ccc.amdahl.com> kls30@duts.ccc.amdahl.com (Kent L Shephard) writes:
   I have a '040 system and I want to print to a file so I can take it to
   my PC and print.

   Now the problem:

   I know I can select print and then save via the save button.  The problem
   is that when I take this file to my PC to be printed it coughs and pukes
   and gives me an error.

Kent, what errors does it give you?

   I'm using a software postscript interpretor.  This should not be the
   problem because I can take postscript files generated by programs on my
   pc and print them fine.  I can do the same with Mac files.  If I take
   a postscript file from my PC to my NeXT and use the postscript viewer to
   look at it everything is fine.

Not too surprising, but the PostScript interpreter on the NeXT is
pretty robust and quite forgiving.

   The one thing I did notice is that a Postscript file with no graphics
   generated by my PC word processor (Wordstar 5.5) is only slightly larger
   than the original text file.   On the NeXT a file generated by WordPerfect
   is 10 times larger. So what's the deal????  

Kent, the NeXT constructs a fairly complicated (read powerful)
PostScript file when you travel by means of the Save button in the
Print panel. One way to see this is to create a file in Edit, say,
with the text "Hello World", click Print, click Save, then rename the
file without the "ps" file extension and you can read the file like a
normal ASCII file. It's quite instructive to read.

   Is ther a specific way to
   print to a file so it looks like the other types of postscript files
   I've seen.

There may be some PostScript compatibility problems... we need to see
those errors..