🚀 go-pugleaf

Andrea,

You can try to reduce the resolution settings in Distiller. That might 
help. Might not. In Frame: I'll bet that the graphics are probably 
embedded rather than imported by reference. That can really eat into the 
memory FrameMaker has. If so you can see if you can get original 
graphics and re-import by reference.

Mike

Andrea,

There are several issues that you may be hitting. 

First, have you applied the Microsoft hotfix to prevent the text
dropout (as described in earlier posts and in Vivek Jain's blog - see
http://www.adobeforums.com/webx/.59b5ba92/0

Is your FM version fully patched?

Have you tried printing to the Distiller printer instance (Adobe PDF)
directly instead of using the Save As PDF route?

Do you have adequate resources (RAM and free diskspace) on your
machine? Have you rebooted your system?

Hi,
First, the graphics are definitely referenced and not embedded. I did attempt changing the distiller resolution settings, but that didn't help.

FM is fully patched. I did attempt to create the PDF both from my standard printer (which works for all the other documents here) and using the Adobe PDF. I also attempted the 2-step PDF process, but that doesn't work consistently (it worked the first time, but seems to fail after that). The machine is a brand new (yay) 4-quad machine and the process barely touches 25%. On my old machine that was definitely an issue. Reboots didn't help.

I haven't installed the hotfix, though I requested it last night when I finally found a thread related to this issue. I'm not getting a crash of any sort, just the missing text. The MS site seemed to indicate it was for a problem that resulted in a crash, but I'm ready to try the fix today. Anyone have any experiences with the hotfix (good or bad)?

Andrea

Well. I did redo the book with a few different distiller settings in the 2-step process. Right now it is working. It didn't before, so this book is definitely inconsistent. I'd still like to hear from anyone who installed the hotfix, because this book will probably "act up" again. :)
Thanks for the help. It made me try something again that didn't work before, but maybe the new machine is helping, too.
Andrea

Andrea,

The MS hotfix seemed to fix the issue on several systems I was using. Just as important, it didn't break anything.

If you elect not to apply it, try the old work-around. Delete the fntcache.dat file in your windows/system32/ directory and then reboot to force a cache rebuild. Generate the PDF before you open any browser windows or other apps that may also use the font cache.

Art

Hi Art. I saw the .dat file fix yesterday, but didn't want to deal with that unless I really had to given how much of a pain it will be with my current work environment, but I'll apply the hotfix today. Glad to hear that it didn't break anything.

Andrea

Andrea,

I've applied the hotfix and it works as expected - no more text
dropouts. Nothing else broke either on several systems.

What is your "standard printer" that you're trying to use to create a
PDF from and what exactly is the process (step-by-step) that you're
using to create a PDF with this?

FYI, the only "device" that should be used to create PDFs is the Adobe
PDF printer instance (this is what Save As PDF also uses). Postscript
(the intermediate file used for distilling) is device dependent and
the Adobe PDF printer instance is specifically designed for the
capabilities of a PDF file. Distilling postscript meant for a
different device can create all sorts of peculiarities in your
resulting PDF.

Hi,
The hotfix seems to have worked. Only time will tell with this book, but I was able to repeat the Save as PDF process multiple times and the book processed completely.

Arnis, we have a dedicated pubs printer here with the Acrobat drivers and our fonts loaded. It is basically the same as using the PDF print driver. Either way was broken without the hotfix, and we've never had problems with any other documents.

Thanks to all for the help.
Andrea