[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: framers@xxxxxxxxx, framers@xxxxxxxxxxxxxx
Subject: RE: mysterious unresolved cross reference
From: hedley_finger@xxxxxxxxxxx
Date: Wed, 16 Jun 2004 12:49:52 +1000
Delivered-to: jeremyg-freeframers:org-ffarchiv@freeframers.org
In-reply-to: <LYRIS-162208-1042851-2004.06.14-22.11.26--hedley_finger#myob.com.au@lists.FrameUsers.com>
Sender: owner-framers@xxxxxxxxx
Paul: > When updating a book, I see one unresolved cross-reference. When I try > searching the file in question for the offending unresolved cross-reference, > FrameMaker fails to find it. The file itself has a text inset. Could FM be > relating to the text inset as an unresolved xref? The Book Error report is busted. One reason it might report unresolved xrefs is that the target is hidden by a condition, in which case the xref should also be hidden by the same condition. In my experience, the Book Error report will still include an unresolved xref even when both xref and target are hidden. You are much better off to generate a list of unresolved xrefs and include this file as a standard fixture in all your books. It correctly reports only true broken xrefs visible on body pages. Regards, Hedley -- Hedley Finger Technical Communications Support Specialist MYOB Australia <http://www.myob.com.au/> P.O. box 371 Blackburn VIC 3130 Australia 12 Wesley Court Tally Ho Business Park East Burwood VIC 3151 Australia <mailto:hedley_finger [at] myob [dot] com [dot] au> Tel. +61 3 9222 9992 x 7421, Mob. (cell) +61 412 461 558 (C) MYOB Limited 2004 ** To unsubscribe, send a message to majordomo@xxxxxxxxx ** ** with "unsubscribe framers" (no quotes) in the body. **