On 08/03/2010 12:21 PM, a.l.e wrote: >> >> There is often a need to produce quickly a print of a file. While in >> production, we can produce dozens of proofs for various reasons and at >> various levels: creation, to see, compare, test; production to check >> overall >> quality, look for defaults, all of those being internal proofs; and we >> have >> the proofs that go to the client, come back with notes, changes, >> corrections, all of various levels. One way to accelerate the printing >> process is to get temporarily rid of the high res images and simply print >> the pages with low res images (depending on what you need to proof, of >> course). >> >> There are various ways to print a proof without the images or with the >> low >> res images. The fastest we found over the years was to temporarily "hide" >> the image folder (putting it elsewhere on another level) so the >> application >> doesn?t know where to find the images, asks a simple question through a >> warning: "Print anyway" or "Find missing images" (and of course, >> "Cancel"). >> When you hit the "Print anyway" button, the job just prints, quickly. >> There >> is basically not much left to process when you take away the images. >> In this >> case, the trick won?t work in Scribus. >> > > > another way of doing, would be to create a script which generates a > preview for each image which does not have one and switches all the > paths... should be easy to do...
One question would be whether this is a Scribus issue or a workflow issue. One answer could come from putting all images on an "image" layer, then choosing to print/export this layer or not. Of course, when Scribus becomes the industry standard, then other possibilities will arise. Greg
