🚀 go-pugleaf

In article <1115@chinacat.Unicom.COM>, woody@chinacat.Unicom.COM (Woody
Baker @ Eagle Signal) writes:
> In article <1837@diamond2.UUCP>, derosa@motcid.UUCP (John DeRosa) writes:
> > henry@angel.Sun.COM (Henry McGilton--Software Products -- R.I.P.) writes:
> > 
> > >In article <1816@diamond2.UUCP>, derosa@motcid.UUCP (John DeRosa) writes:
> > >    *  ......code starting with #! Adobe.
> > >Chances are some prolog file is missing from the Mac version.
> > 
> > No, that's not it.  To start with, this is a sun document in PS.
> > I get it to the Mac and can download it to the Laser just fine.
> > But, if I just try to print it (i.e. using a text editor) I don't
> > get the real document, I get a listing of the PS code.  It would 
> 
> This is just as it should be.  The text editor is probably using a laser
> driver.  On the MAC, I think that if you print a file from an editor, it
> goes through a filter that converts it to text.  The fact that you can
> download it to the laser and it prints the picture, but you print it from
> the editor and get a listing is diagnostic of this.
> 
Not exactly. It IS text, so you don't have to filter it to text. The difference
is some other operating systems use the first couple of bytes in a file to
determine the file type. The Mac stores file type information somewhere else
(not as part of the "text"). To a Mac program, the file is of type TEXT,
and hence is printed as such. A counter-example: Adobe Illustrator stores its
PostScript in plain text, but the file is tagged as "belonging" to Illustrator.

Philip Machanick
philip@pescadero.stanford.edu