Path: utzoo!attcan!uunet!mcsun!i2unix!inria!seti!fantasio.inria.fr!collet
From: collet@fantasio.inria.fr (Pierre Collet)
Newsgroups: comp.windows.ms
Subject: Re: Problems with PostScript/Win3
Message-ID: <1990Sep13.113749@fantasio.inria.fr>
Date: 13 Sep 90 09:37:49 GMT
Sender: news@seti.inria.fr
Reply-To: jorge@dg-rtp.dg.com (Jorge Lach)
Organization: Institut National de Recherche en Informatique et Automatique -- Rocquencourt, France
Lines: 35



>I cannot print postscript files that have been saved to disk. When
>I was using Win 2.11, I could save postscript output to a file (by
>connecting the ps printer to output.prn), and then take that file on
>a floppy, upload it to my Unix system, get rid of the extra ^M's, and
>send it to an Imagen printer, which has an "Ultrascript" interpreter.
>After I upgraded to Win3, I cannot longer do that. I can save my files
>ok, but the postscript header does not resemble the old at all.


I didn't find any problems with Windows 3.0. I think you should prefer
"Postcript" driver to any other driver as it will be more standard.

Whenever this option was not available, I chose "Laserwriter II/NTX" as
it is the printer I always use.

I wrote a small shell script to translate the files for UNIX so that ^Ms
and ^Ds don't disturb the printer. The rest is quite strqightforward as
I simply type :
$ lpr file
to get the job done.

Here is the dos2unix script :

$cat dos2unix
sed -e s/^D//g $1 > foo
sed -e s/^M//g foo > $1
rm foo
$

It may not be very elegant but it had the best
efficiency/development_time ratio I could find :-> !

Good luck !