Ken Sharp <ken.sh...@artifex.com> writes: > Well its certainly going to be hindered by my own lack of understanding :-) > > What I had hoped was to do what David had said in the comment you > quoted; rework the whole interaction with Ghostscript. Obviously > that's not going to happen, so we'll have to try and work with what we > have.
The interaction with GhostScript involves "please render now page xxx into a PNG file". This interaction is done in a pipe, the order is not known in advance but depends on the viewing behavior of the user. pdf2dsc solves the task of splitting the PDF processing into one per-document block of resources that are loaded in advance and into per-page rendering instructions. Th bulk of this is essentially guaranteed to be stable by how DSC is defined as an interoperability standard. Last time I looked (admittedly quite some time ago), I have not found anything in GhostScript that provides similar (and documented!) stability for PDF processing of individual pages efficiently and in dynamically determined order. -- David Kastrup
