Yes, this is indeed a known issue, although at this point
we don't know exactly what the cause of the problem is.

We do know that (1) it is not necessarily repeatable between
two identically-configured systems or even on the same system
and (2) there is a hack to at least temporarily "fix" the

This fix is as follows:

(a)     Exit all applications

(b)     Delete file <C:\WINDOWS\system32\FNTCACHE.DAT>

(c)     Reboot

Upon rebooting, the system font cache is rebuilt as needed by
Windows. And according to those who have tried this "fix," the
problem is gone, at least for a while.

Since there is nothing that FrameMaker as a program can do to
corrupt that system file or even open it, the problems are
probably secondary to some issue associated with FrameMaker's
novel use of its own character set in combination with standard
Windows GDI calls.

If you really want to be defensive, one thing you could do would
be to write a script that deletes that font cache file every time
you power down your system.

Let us know if this solves the issue for you.

        - Dov

> -----Original Message-----
> From: Alison Carrico
> Sent: Wednesday, May 16, 2007 1:59 PM
> I have an intermittent, but incredibly annoying, problem with 
> PDFs printed from Frame missing large chunks of text at 
> random.  Sometimes it is  just a few words out of a 
> paragraph, sometimes it's the whole paragraph. Some time ago, 
> I found an article on Adobe's support site that addressed the 
> issue, but I can no longer reach that page. The "Knowledge 
> Base" search returns a link to it, but the link gives a "page 
> not found" error (quite a number of pages return errors).  
> One of the solutions was to change the Graphic Print Quality 
> setting in the printer properties to 300 dpi, which works 
> some of the time.
> Sometimes, I can restart either Frame or my machine and print 
> successfully. Sometimes I can use a different machine.  
> Sometimes, I can save the file as MIF and print.  
> Unfortunately, not one of these tricks always works so I'm 
> looking for a more reliable workaround or perhaps (dare I 
> hope?) even a permanent solution.  
> Is anyone familiar with this problem?  Any help would be much 
> appreciated.  
> Thanks!
> alison

Reply via email to