Newsgroups: comp.lang.postscript
Path: utzoo!utgpu!watserv1!desh
From: desh@watserv1.waterloo.edu (Desh D. Sharma)
Subject: Re: lpr and PostScript?
Message-ID: <1990Aug16.131737.4134@watserv1.waterloo.edu>
Keywords: lpr, Postscript
Organization: University of Waterloo
References: <23632@dartvax.Dartmouth.EDU> <2445@mcrware.UUCP> <673@vidiot.UUCP>
Distribution: na
Date: Thu, 16 Aug 90 13:17:37 GMT
Lines: 29

In article <673@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes:
> In article <2445@mcrware.UUCP> steves@mcrware.UUCP (Steve Simpson) writes:
> <
> <Your Postscript file should have a .ps extension and you can lpr it directly
> <to you PS printer.
> 
> As far as I have every noticed, on either a 4.3BSD system, or my current
> AT&T SysV 3.2 system, the name of the file is unimportant.  The .ps extension
> means nothing to the printer spooler.

Sorry, I have lost the name of the person that originally asked the question.

Anyway, this problem seems to be a case of probably a filtering program 
(setup as default in the printcap entry for the printer) that seems to be
grabbing the file given it, wrapping some standard ASCII-to-PS code around
it, and sending the result off to the printer.  What you have to do is to tell
lpr to use the literal switch so that this does not occur. On some older
lpr's it used to be "-l", or some fixed and better written ones the "-Fl"
switch is used.  i.e.   lpr -Plaser -Fl foobar.ps

I don't think that the .ps extension should have any effect at all, but let's
be consistent anyway.

....desh
-- 
-=-=-=-=
Desh D. Sharma, Arts Computing Office, Univ. of Waterloo, Waterloo, ON. CANADA
    Internet:  ddsharma@watmath.waterloo.edu | desh@watserv1.waterloo.edu 
      BITNET:  DESH@WATDCS .OR. DESH@WATACO