Mystery text inset error

Report · May 16, 2012

Using FM 8.0p277 on Windows XP. I have a large book (474 pages, 24 files) that has chapter-level TOC files that are imported into the beginning of each chapter file.

When I rebuild the book, I get five error messages that read similar to the following:

C:\MyDocs\My Guide\Releases\Release A\MyChapter1.fm

Unresolved Text Inset (from source file: MyChapter1TOC.fm).

The "MyDocs\My Guide" path and the file name are wrong - they reflect a different version of the book that is no longer used (but the folder/files are in the location).

If I search for unresolved text insets, there are none.
The TOC file correctly references the file in the new location/with new name.
There is no reference to the wrong path/name in the MIF files for the chapter or TOC files.
If I delete the TOC file and re-gen. and re-import it, then re-gen. the book, I still get the error.

However, the wrong path IS referenced in the book's MIF file - similar to the following:

<XRefSrcFile `<c\>Releases<c\>Release A<c\>My Chapter.fm'>

I looked in the MIF for the above chapter and found a ref. marker with the number cited, 21725.

I'm sure if I look in the other four files I will find similar.

What is the best way to fix this?

a) manually change the book file code in the MIF file (change to reference the correct file)?

b) ???

The incorrect info in the book file seems to have nothing to do with the TOC file, so I'm very confused. The book seems to generate correctly but I hate to have error messages and I'd like to clean this up.

Thanks for your help.

Report · May 17, 2012

> If I search for unresolved text insets, there are none.

Did you search on Master and Reference pages, or just Body?

Are there any expected text insets anywhere?

If so, and they are from other Frame Flows, they could be including their own insets.

If the inset contains para tags that are included in TOC gen, references to them might well end up in the TOC.

Report · May 17, 2012

Thanks for attempting to help. To answer your questions, yes, I searched master and ref. pages. And yes, there are expected insets, the TOC files at the beginning of each chapter.

I solved this problem, not sure which of the following two actions gets the credit, but I suspect it's the second.

First, I used a new tact for re-importing the TOC files. I selected the existing text inset and then selected File > Import > File. In the past I deleted the inset then imported the file again, or I updated the inset; I did not select the existing inset and re-import.

Second, I renamed the old (wrong) folder that was referenced in the error messages. After regenerating the book, I had no text inset errors - instead unresolved cross ref.s were listed. These unresolved ref's were to the same files that were listed as text inset errors -- pointing to the old folders/files. Once I corrected those cross ref's, the book generates with no errors.

Go figure.