home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.apps:8346 comp.os.ms-windows.apps:4939
- Newsgroups: comp.os.os2.apps,comp.os.ms-windows.apps
- Path: sparky!uunet!ukma!wupost!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!swimming.cis.ohio-state.edu!grichard
- From: grichard@swimming.cis.ohio-state.edu (Golden Richard III)
- Subject: Amipro postscript problem?
- Message-ID: <1992Nov16.214333.27005@cis.ohio-state.edu>
- Sender: news@cis.ohio-state.edu (NETnews )
- Organization: The Ohio State University Dept. of Computer and Info. Science
- Date: Mon, 16 Nov 1992 21:43:33 GMT
- Lines: 33
-
-
-
- Has anyone had problems with Amipro 3.0 generating incorrect
- postscript output? If so, I'd really appreciate Email (or, if you've
- generated mountains of the type of output I describe below and have
- had no problems, your input might also help...)
-
- I'm running Amipro under OS/2's WINOS2 environment, but I'm posting to
- both ms-windows and os2 newsgroups because the real question is
- whether there's a problem with Amipro itself or with OS/2's WINOS2
- Postscript driver.
-
- Problem:
-
- Sometimes when images created using Amipro's draw mode are
- interspersed with text, bad postscript is generated. Several
- postscript printers refuse to print the resulting file and ghostscript
- dies with a setlinecap error. If the image is placed in a file by
- itself and printed, 99% of the time it will print ok. Sometimes the
- image is slightly garbled. I've also had Amipro generate bad
- postscript once for a footnote.
-
- Since I use Amipro as my technical document editor, this is a *very*
- major problem.
-
- Any ideas?
-
-
-
- --Golden
- --
- Golden Richard III OSU Dept. of Computer and Information Science
- grichard@cis.ohio-state.edu (614) 292-0056
-