Without knowing more about your environment, I would try Bruce
Foster's Archive plugin to collect and submit files. It would be an
easy way to make things work, and make the process simple. The plugin
will resolve cross-refs and also set up a common directory structure
that you can easily import.
A suggestion:
Get and use the BookUtils plug-in. Or save as MIF and do find and replace
searches to correct Xrefs.
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL PROTECTED]
To unsubscribe send a blank em
Fred Ridder; Kelly McDaniel; framers@lists.frameusers.com
Subject: RE: Broken xrefs
Fred Ridder wrote:
> FrameMaker only knows to update generated files that have the
> same base filename as the book plus the relevant generated
> file suffix (e.g.
> ...TOC, ...LOF, ...IX). If the names of the exis
ailto:[EMAIL PROTECTED]
Sent: Friday, September 14, 2007 2:48 PM
To: Fred Ridder; Kelly McDaniel; framers@lists.frameusers.com
Subject: RE: Broken xrefs
Fred Ridder wrote:
> FrameMaker only knows to update generated files that have the
> same base filename as the book plus the relevant genera
Fred Ridder wrote:
> FrameMaker only knows to update generated files that have the
> same base filename as the book plus the relevant generated
> file suffix (e.g.
> ...TOC, ...LOF, ...IX). If the names of the existing
> generated files don't follow the pattern, FrameMaker will
> generate bran
It may be water under the bridge, but if you change the filenames
*within* FrameMaker, in the book window, FrameMaker automatically
updates all the references for you. No broken links. If you make the
changes in Windows (outside of FrameMaker), however, FM doesn't
know that the filenames has chang
