[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Mitchell, Sue" <Sue.Mitchell@xxxxxxxxxx>, <hedley_finger@xxxxxxxxxxx>, <framers@xxxxxxxxx>, <framers@xxxxxxxxxxxxxx>
Subject: RE: mysterious unresolved cross reference
From: "Chulsky, Mark" <mchulsky@xxxxxx>
Date: Wed, 16 Jun 2004 09:13:02 -0400
Delivered-to: jeremyg-freeframers:org-ffarchiv@freeframers.org
Sender: owner-framers@xxxxxxxxx
Thread-index: AcRTTXoT1aW7dqp3R06bGXwarkG8wQAU8ZbwAACHkSA=
Thread-topic: mysterious unresolved cross reference
If the tricks suggested by Hedley and Sue do not help, try to search the Master pages for the broken x-refs. Good luck, Mark Chulsky, Mercury Computer Systems 978-967-1407 > -----Original Message----- > From: owner-framers@xxxxxxxxx > [mailto:owner-framers@xxxxxxxxx] On Behalf Of Mitchell, Sue > Sent: Wednesday, June 16, 2004 8:55 AM > To: hedley_finger@xxxxxxxxxxx; framers@xxxxxxxxx; > framers@xxxxxxxxxxxxxx > Subject: RE: mysterious unresolved cross reference > > I seem to remember that it actually depended on the order in > which you hid the xrefs. If you hide the target first then > you get the unresolved message in the Book Error report. If > you do it the other way around all is fine. > > -----Original Message----- > From: owner-framers@xxxxxxxxx [mailto:owner-framers@xxxxxxxxx] > Sent: Tuesday, June 15, 2004 10:50 PM > To: framers@xxxxxxxxx; framers@xxxxxxxxxxxxxx > Subject: RE: mysterious unresolved cross reference > > > > 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. ** > > This message may contain privileged and/or > confidential information. If you have received this e-mail > in error or are not the intended recipient, you may not use, > copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender promptly by e-mail that you have done so. > Thank you. > > > > ** To unsubscribe, send a message to majordomo@xxxxxxxxx ** > ** with "unsubscribe framers" (no quotes) in the body. ** > ** To unsubscribe, send a message to majordomo@xxxxxxxxx ** ** with "unsubscribe framers" (no quotes) in the body. **