🚀 go-pugleaf

Edwin,

Since you are configuring an automated system, I am guessing you need a solution that doesn't involve manual tweaking in the middle of the publishing process. I would add to Rick's suggestion that you use FrameScript to change the View > Options setting dynamic ally, once the document has been parsed and is fully loaded in Frame. At least you could see what is really slowing down the processing. You might be surprised to find out that it is not the image rendering.

If the rendering does happen to be the reason behind the slow response, you could reference a low-resolution version of your images when you first load the XML file, then you save a MIF file and close the document. Finally, you process the MIF text file to change the reference to the high-resolution images and open the resulting MIF file in Frame Server. It doesn't go through the full parsing any more, so it doesn't take as long. And then you are all set to print. All this can be automated using FrameScript.

However, what has worked for me in more than one occasion is my last suggestion: make your documents smaller. You can break them down into documents of lower-level elements (chapters, sections, or whatever structural component is available below your current document level). This really helps reduce the time FrameMaker takes to parse and load files. You will probably see that the difference is literally exponential.

Regards,
Juan Souza