Article View: comp.lang.postscript
Article #1367Re: Bad PostScript by Windows.
From: Laura Halliday
Date: Fri, 24 Nov 1989 21:56
Date: Fri, 24 Nov 1989 21:56
12 lines
945 bytes
945 bytes
Though I haven't seen the PostScript Windows cranks out, I've certainly seen what MS Word 5 cranks out. No fun. Do people have any favourite `acid tests' they use to get some idea of PostScript compatibility? My current one is to download the PostScript file onto our NeXT and let Preview image it. It's the only non-LaserWriter PostScript implementation I have access to, and the results can be useful. ...laura
Technical Details
Message-ID:
<5769@ubc-cs.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!aplcen!samsung!cs.utexas.edu!rice!uw-beaver!ubc-cs!cheddar.cc.ubc.ca!hallidayReferences:
<12877@polya.Stanford.EDU> <1529@cc.helsinki.fi>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!aplcen!samsung!cs.utexas.edu!rice!uw-beaver!ubc-cs!cheddar.cc.ubc.ca!halliday From: halliday@cheddar.cc.ubc.ca (Laura Halliday) Newsgroups: comp.lang.postscript Subject: Re: Bad PostScript by Windows. Summary: Ouch. Message-ID: <5769@ubc-cs.UUCP> Date: 24 Nov 89 21:56:34 GMT References: <12877@polya.Stanford.EDU> <1529@cc.helsinki.fi> Sender: news@cs.ubc.ca Reply-To: halliday@cc.ubc.ca (Laura Halliday) Organization: UBC Computing Centre, Vancouver, B.C., Canada Lines: 12