We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
My top level is DOC. Inside that I have BODY, and inside that I have my chapters. The first one is now showing up in the structure as BOOK-COMPONENT. How do I get it back to being a chapter?
When you add a file to a book, FM does not actually open the file to see what it contains. At that point, the file is shown in the Structure View for the book as you've noted as BOOK-COMPONENT. When you update the book, however, FM opens the book component. If its main flow is structured, FM relabels the bubble in the structure view with the tag of the highest-level element ("chapter", in your case). If the main flow is unstructured, as will be the case for a generated file such as a table of contents or index, the bubble retains the BOOK-COMPONENT label. In short, all you need to do is update the book.
I get all that and your answer makes sense. What is puzzling is how it lost its chapter definition. I’ll try the update and hope for the best. Thanks for your prompt reply and patience.
I ran the update, but it didn’t restore the chapter definition.
The only way I have been able to make filenames switch back to BOOK-COMPONENT is:
Since the labels are stored in the book file rather than the book components themselves, this behavior makes sense. For them to be persistent, you must save the book after they are assigned.
Thanks for the explanation, Lynne. It doesn’t surprise me that something went weird.
Can you help me figure out how to get the Chapter back to being a Chapter? When I open it, there’s no structure.
If the Structure View is empty when you open the file, then the document's main flow is unstructured. Unstructured documents also show in the book's Structure View as BOOK-COMPONENT.
If the flow has been unstructured, you may be able to use a conversion table to regenerate some structure, but you will most likely need to clean up the results.
For those of you following this discussion, Tony has confirmed that the document is unstructured. He suspects that someone using the unstructured FrameMaker user interface opened the file and saved it (ignoring the warning that doing so might lose information). He plans to recreate recent changes in a backup of the structured file.
Thanks, Lynne. I’ve succeeded in doing that.