Path: utzoo!attcan!uunet!aplcen!samsung!usc!apple!agate!ucbvax!bloom-beacon!eru!luth!sunic!tut!hydra!hylka!tarkkonen
From: TARKKONEN@cc.helsinki.fi (Lauri Tarkkonen)
Newsgroups: comp.lang.postscript
Subject: Re: Bad PostScript by Windows.
Message-ID: <1529@cc.helsinki.fi>
Date: 24 Nov 89 17:41:55 GMT
References: <12877@polya.Stanford.EDU>
Followup-To: comp.lang.postscript
Organization: University of Helsinki
Lines: 24

In article <12877@polya.Stanford.EDU>, rokicki@polya.Stanford.EDU (Tomas G. Rokicki) writes:
> After seeing yet another sample of *lousy* PostScript generated by an
> application (this one Windows Designer), I'm very upset.  This particular
> application makes *no* effort to comply with any structuring conventions.
> It even generates an unprotected call to `a4'.
> 

They are in good company, I tried to use windows generated postscript 
files as a part of output generated in some other programs, the failure
is inevitable, because whoever wrote the windows postscript driver 
(I hope Microsoft is listnening) has probably by purpose made the driver
obsolete, by using commands like "setmatrix", that will for sure destroy
the other parts of the page and make the whole exercise obsolete. I think
that they deliberately have not followed the structuring conventions and
advises given by  ADOBE. I guess we should not blame ADOBE for this.
The experiments with the DESIGNER created PostScript files have been 
similar. One could of course patch the PostScript file by hand or by
a program, by would it not be reasonable to expect, that a postscript
file created by windows or some applications were not obsolete. The 
code created by these applications is very slow, about 10 to 30 times
slower than simnilar pages created by some other programs.

Lauri Tarkkonen
University of Helsinki