Thanks Fred. I've been informed that your solution was right on the money.
Alison Alison Craig | Technical Documentation Lead Ultrasonix | 130-4311 Viking Way | Richmond, BC V6V 2K9 | analogicultrasound.com<http://www.analogicultrasound.com> T 604-279-8550 ext 127 | F 604-279-8559 From: Fred Ridder [mailto:[email protected]] Sent: Thursday, March 13, 2014 2:46 PM To: Craig, Alison; [email protected] Subject: RE: TOC Failure There are only two things that are special about a TOC file: * It *usually* has a filename that it the same as the book file but with "TOC" appended before the ".fm" extension. * It is added to the book as a generated file (Add>Table of Contents) and *NOT* as a component file (Add>File). Otherwise, it's just a file that happens to contain a whole bunch of autogenerated cross-references to all the headings in the document. The most likely scenario is that somebody accidentally deleted the TOC from the book file, and then replaced the generated file with a static content file using Add>File. It's easy to get confused on this, because the TOC file will still be present in the file system and it seems obvious (but wrong...) to just re-add the file. The fix is to delete the static file entry from the book file and re-add a table of contents. Do *not* delete the actual TOC file from the file system; the file itself is just the same as it was before it was changed to a static component. When re-adding the TOC, it's optional whether you allow FrameMaker to update the book and regenerate the TOC, but if you do perform an update it should turn out to be formatted exactly as the previous TOC was (as long as nobody trashed the file for the previous TOC). -Fred Ridder ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: TOC Failure Date: Thu, 13 Mar 2014 21:20:09 +0000 I received a request for help from my counterparts at a sister company in Denmark. I know they are running unstructured Frame 9 and should be all patched at this point. At least one system is a 64 bit Windows 7 Pro machine. The issue is a TOC file that is no longer a TOC file. It's simply registering as a regular FM file in the book, although it used to be a proper TOC file that updated just fine when required. Can anyone tell me: * why - and how - would a TOC file stop being a TOC file? * short of simply recreating a new TOC file, is there a way to salvage the existing file and turn it back into an updatable TOC? Thanks, Alison Alison Craig | Technical Documentation Lead Ultrasonix | 130-4311 Viking Way | Richmond, BC V6V 2K9 | analogicultrasound.com<http://www.analogicultrasound.com> T 604-279-8550 ext 127 | F 604-279-8559 _______________________________________________ You are currently subscribed to framers as [email protected]<mailto:[email protected]>. Send list messages to [email protected]<mailto:[email protected]>. To unsubscribe send a blank email to [email protected]<mailto:[email protected]> or visit http://lists.frameusers.com/mailman/options/framers/docudoc%40hotmail.com Send administrative questions to [email protected]<mailto:[email protected]>. Visit http://www.frameusers.com/ for more resources and info.
_______________________________________________ You are currently subscribed to framers as [email protected]. Send list messages to [email protected]. To unsubscribe send a blank email to [email protected] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [email protected]. Visit http://www.frameusers.com/ for more resources and info.
