On 5/26/2011 9:28 PM, Karen Robbins wrote:
Every file generates a missing font message! But if that were the cause
of the index problem, wouldn't Frame stop background-file-opening at the
first flawed file it encountered in the book? Instead, Frame goes
through several files before the error
Hello Framers,
I cannot generate an index from my book file. The book error log
reads Couldn't update this book, because it contains no openable
nongenerated files. It doesn't name a document file that caused the
problem, only the book file itself.
I am certain that the 13 files in my book
Karen Robbins wrote:
I cannot generate an index from my book file. The book error log
reads Couldn't update this book, because it contains no openable
nongenerated files. It doesn't name a document file that caused the
problem, only the book file itself.
I am certain that the 13 files in
Richard,
Yay! Opening all the files at once worked. You hit it on the head,
something is causing FrameMaker to not be able to open all the files
in the background. Where would I start looking?
thanks for the workaround,
Karen
At 4:12 PM -0700 5/26/11, Combs, Richard wrote:
So, did you try
Karen Robbins wrote:
Richard,
Yay! Opening all the files at once worked. You hit it on the head,
something is causing FrameMaker to not be able to open all the files
in the background. Where would I start looking?
When you open a file with an error condition, FM should display a dialog
Every file generates a missing font message! But if that were the
cause of the index problem, wouldn't Frame stop
background-file-opening at the first flawed file it encountered in
the book? Instead, Frame goes through several files before the error
message appears and the operation stops. And
Karen Robbins wrote:
I have painstakingly migrated from Type 1 fonts to Open Type fonts,
and equally carefully installed the new fonts on several machines. We
have long dealt with false missing font errors. Of course I'll make a
final pass for font irregularities, but there has never been
Karen Robbins wrote:
> I have painstakingly migrated from Type 1 fonts to Open Type fonts,
> and equally carefully installed the new fonts on several machines. We
> have long dealt with false missing font errors. Of course I'll make a
> final pass for font irregularities, but there has never been
