[fa.laser-lovers] dvi2ps and memory fill up

laser-lovers@uw-beaver (07/21/85)

From: Neal Holtz <holtz%cascade.carleton.cdn%ubc.csnet@csnet-relay.arpa>

Then I will also reply to the net:


==================
        Delivery-date: Friday, July 19, 1985 at 16:09 ADT
        From: Neal Holtz <holtz@cascade.carleton.cdn>
        To: Robert Morris <ram@umass-boston.csnet>
        In-Reply-To: dvi2ps:48
        Message-ID: dvi2ps:49
        Subject: Re:  dvi2ps Users?  - quick way to increase capacity (# of pages)
        
        Your analysis is substantially correct.  The context is that dvi2ps is a quick
        and dirty way to get TeX output on a LaserWriter -- it downloads all
        the TeX fonts and does not use any of the resident ones.  Horrible, I know,
        but pleasingly effective (3 pages/minute on long documents).
        
        The structure of the downloaded PS code for every page in the document is:
        
                -    start-of-page
                -    down load all new char bitmaps for that page
                -    save
                -    down load all typesetting instructions (strings, etc.)
                -    restore
        
        It does reclaim considerable VM after every page, but obviously not
        the bitmap downloading.  That has to be done outside the save/restores
        (I think), or else you have to download all chars every page (instead of
        each char only once)  -- that would be too expensive.
        
        So what happens is that VM eventually fills with downloaded chars and font
        dictionaries -- so that was why the suggestion of 'note' pagestyle.