Bart:
> I have learned to keep in mind that it also matters to one's printer.
>
>; Lesson learned when I dragged 12 large photos (jpg) down enough in size so
> that I could get them all on one Letter-size sheet.
This one I've heard about before. I'm curious to know more about it.
What's the equipment involved? The only PostScript printer I have is an
old HP B&W inkjet(!) that sits in a closet. I used it up to around 2000
and, in those days it was mostly with my Amiga and mostly many fewer
images. My experience "ripping" (if that's the right word) PDFs tells me
that dragging an image to a smaller size reduces the usable resolution
when you print, but that the full-size image is still in the PDF and,
presumably, it would be part of a PostScript file as well. So, it's
understandable that the PostScript file would grow in size even with
typical JPEGs or other compression schemes.
Where does "out of memory" come from, though? From the little I know
from experience, the file is probably processed within the printer
itself, so the message could be generated from communication between the
printer and the computer when the printer hits the wall. If, on the
other hand, one is using something like an inkjet with an external
PostScript engine (which was common for a while), then I'm guessing that
the memory limitation would be in the computer. However, on most PCs I
would expect it to be channeled to the computer's virtual memory and the
limitation would be hard disk space. On a Windows PC, you would
eventually get an enlarging-virtual-memory message instead of
an-out-of-memory message (probably), and the darn thing would print
sometime the next day.
As far as printing 12 or more images on a page, I've only down that with
photo catalogs, and then only once or twice. Cataloging programs
normally will take care of the whole job, providing suitable captions
and employing thumbnails for the pictures. But since you're going to
PostScript from PageStream, you're obviously not doing that. Are the
images originating from full-resolution files? If so, that seems a waste
of bandwidth. But creating separate versions for the documents is
likewise a waste of your human bandwidth if it can avoided.
Any insights anyone?
HB
.
