Article View: comp.text
Article #5868Re: Large postscript files to a laserwriter
From: Chris Maltby
Date: Thu, 23 Feb 1989 02:48
Date: Thu, 23 Feb 1989 02:48
14 lines
1212 bytes
1212 bytes
The "bug" is caused by a design problem with garbage collection. Postscript jobs tend to accumulate fonts, and other junk as they execute. The best generic solution is to embed each page of text between a restore/save pair, and save the empty environment at start time. By restoring to the empty saved environment and then saving it again you can cause the VM garbage collection to work much better. Permanent fonts can be stored by restoring (to the backgroun environment) defining the font and then saving. Try it, it works. I have no troble printing huge troff documents with pic's tbl's and eqn's using such a system... -- Chris Maltby - Softway Pty Ltd (chris@softway.oz) PHONE: +61-2-698-2322 UUCP: uunet!softway.oz!chris FAX: +61-2-699-9174 INTERNET: chris@softway.oz.au
Technical Details
Message-ID:
<1175@softway.oz>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari!otc!softway!chrisReferences:
<1936@goanna.oz> <3660@cidam.rmit.oz>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari!otc!softway!chris From: chris@softway.oz (Chris Maltby) Newsgroups: comp.text,comp.lang.postscript,aus.tex Subject: Re: Large postscript files to a laserwriter Message-ID: <1175@softway.oz> Date: 23 Feb 89 02:48:54 GMT References: <1936@goanna.oz> <3660@cidam.rmit.oz> Reply-To: chris@softway.oz (Chris Maltby) Organization: Softway Pty Ltd, Sydney, Australia Lines: 14