[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Thomas Michanek <thomas.michanek@xxxxxxxxx>
Subject: Re: Cross-references Won't Update
From: Patricia Gee-Best <pgee@xxxxxxxxxxxxx>
Date: Fri, 12 Nov 1999 17:31:33 -0500
CC: Colin Green <cgreen@xxxxxxxxxxxxxxxx>, framers@xxxxxxxxx
References: <001101bf2ca6$84f9cd20$0333a8c0@rosenstein.telia.com>
Reply-To: pgee@xxxxxxxxxxxxx
Sender: owner-framers@xxxxxxxxx
Thomas/Colin: Also, check for conditional text, and check your master or references pages. Sometimes unresolved references can get buried in these locations. This is where they are usually located when FM tells me I've got unresolved references but they are not found on the body pages. Pat Gee-Best > > >I've gone though and updated all my cross-reverences in a book file, file > >by file, using the Find/Change Unresolved Cross-references functionality. > >I've further checked my work by applied the Update Reference functionality > >to each file. No unresolved cross-references are to be found. > > > >When I regenerate the book, however, a message in the status bar of the > >book file informs me that Frame is updating references in four of my eight > >files in the book. I open those files, search for unresolved reference: > >nothing. > > There is a (un)known bug in Frame concerning the status of > (un)resolved x-refs between book updates and file updates. However, > the effect of that bug is that if you open a document that according > to the book update contains unresolved x-refs and search for them, > the search will find unresolved x-refs that are actually resolved. > The remedy is to first update the x-refs in the individual file > before performing the search; in that way, only the real unresolved > x-refs will be found. > > However, I haven't seen this work the other way around, i.e. that > the book update reports unresolved x-refs that cannot be found... > In any case, try to first update the x-refs in the individual file > before starting the search, and see if they'll be found then. > > The reason for the bug seems to be that a book update doesn't > correctly (re)set the flag for each individual x-ref that FM uses > to find unresolved x-refs. Only when the update is performed in > the individual file, these flags will be (re)set correctly. > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Thomas Michanek, [Michagon], Linkoping, Sweden > Documentation Consultant, FrameMaker/UNIX expert > EMAIL: mailto:Thomas.Michanek@telia.com > WWW 1: http://hem1.passagen.se/framers > WWW 2: http://w1.133.telia.com/~u13304072 (not ready) > - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > ** To unsubscribe, send a message to majordomo@omsys.com ** > ** with "unsubscribe framers" (no quotes) in the body. ** ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **