Hi Elchanan,

If FrameMaker cannot open the target file, this may cause
unresolved cross-references.
Could it be that you have a file in the book which is closed
and which triggers error messages when opened (e.g. missing
fonts).

Does it make a difference, if you open all files of the book?

Best regards

Winfried

From: framers-bounces at lists.frameusers.com 
[mailto:[email protected]] On Behalf Of VLM TechSubs
Sent: Tuesday, October 01, 2013 12:42 AM
To: Framers
Subject: RE: FM 8: Xref markers keep breaking and re-breaking

Perhaps I should add that this just happened when I added an index to the book. 
The process called for a generate, which I did. And now, lots of broken xrefs. 
I did change the index suffix, but I can't imagine that would cause the problem 
... would it?

From: VLM TechSubs [mailto:[email protected]]
Sent: Monday, September 30, 2013 3:41 PM
To: Framers
Subject: FM 8: Xref markers keep breaking and re-breaking

Greetings!

I put xref markers in throughout a book. These markers are simple xrefs to 
other chapters, nothing fancy. I generate the book, all is well. After working 
for a while, I do another generate (sometimes with intervening generates that 
were fine), and all of a sudden, lots of broken xrefs. I fix them all, 
generate, and all is well. Several generates later, poof! A large number of 
broken xrefs again.

Has anyone else encountered something like this?

Thanks,
Elchanan

________________________________

This e-mail contains privileged and confidential information intended for the 
use of the addressees named above. If you are not the intended recipient of 
this e-mail, you are hereby notified that you must not disseminate, copy or 
take any action in respect of any information contained in it. If you have 
received this e-mail in error, please notify the sender immediately by e-mail 
and immediately destroy this e-mail and its attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20131001/de3ac97c/attachment.html>

Reply via email to