Framemaker 2015 - Structured Book

[BrianG_9502]

I have been trying to get a structured book to work in Framemaker 2015. The two chapter files are validated. But I cannot get the 'NoName' element in the book structure to work. How do you rename the 'NoName' element? I have read through a number of the forums and help files.

I started with groups  and files, and couldn't get that to work. From what I saw on the forum, groups and files in a book file may not be functioning features.

My current file is a book file, with two chapters, Chapter2.fm, and Chapter3.fm.

I haven't seen any guide in the Framemaker documentation (8, 9, 10, 12, or 2015) that helps me get this 'structured book' file concept to work.

Is it not possible to create a structured book? or an endeavor that requires developer capabilities?

[Russ Ward · Accepted solution]

BrianG,

It is a little tough for me to understand exactly what obstacle you are facing. Books can be structured and groups/files function correctly. I'll throw out a few tips, perhaps these can lead you to a solution:

- Since you see a structure for your book, that means you have at least imported an EDD. Good. At this point, the management of the structure tree uses the element catalog, just like in a document, except as described in the next point....

- Each file in a book will be automatically represented by an element. This just happens when you add a file to a book. BUT, you can't change those elements manually. They automatically update to the same root element in the respective documents, when you do a book update. So, the book update process is important for updating a book structure tree.

- Groups and folders also get an element in the tree automatically. But unlike files, you can change these tags with the element catalog.

- Every structure tree must have a root element. When you import an EDD into a book, it gets a structure tree, and assigns a NoName tag to the root. It just does this because it doesn't know what element you might want there. All you have to do then is select it in the structure view, then use the element catalog to change it.

I hope this helps some.

Russ

[BrianG_9502]

Russ,

Thank you for responding to my post.

Your tips were helpful. I was able to rename the NoName tag for the book, and now the book structure is validated down through the first few elements after a book update. The book tag and the file I have in the book file for the cover are validated. Now I will need to move on to troubleshoot the Front Matter BOOK-COMPONENT, and the Body BOOK-COMPONENT to see if I can get the structure to work.

Do you know if there are any references available for a structured book besides what is available from the Adobe FrameMaker Templates?

I am attempting to build a fairly complex manual for my first book, and I think it may lead to a number of struggles without some reference files to see what others have employed as best practices.

Another error I get that I haven't determined a solution for is related to inserting non-FrameMaker files into the book. I assumed I could add .pdf files in an Appendix, but I get a 'Could not open filename.pdf because it is not a FrameMaker document errors' for every linked file. Is there a section that would address this issue in the product documentation? Do I need to put some type of EDD tag or file wrapper on each pdf file?

I am not sure what section to start reading.

Brian

[Russ Ward]

Brian,

I don't know of any good information on structured book management. My thought is that a structured book is typically an afterthought in a typical architecture... the data of most concern is in the chapter files. I see a structured book as something of a kludge to adapt the FM book model to the world of markup... some way just to tie it all together, especially if exporting to XML. That's just my opinion, though, based on my general lack of interest in the book structure model.

Regarding front matter files (TOC, etc) and that BOOK-COMPONENT thing... any unstructured file will automatically get the <BOOK-COMPONENT> element. TOCs, etc. are typically unstructured. If you want that element to be valid in the structure view, add <TEXT> to the general rule of the parent element, in the EDD. The <BOOK-COMPONENT> element validates to that.

Regarding PDF files, I don't believe that a native PDF file can reside as a book component, because I don't believe that FM can natively open a PDF file. I know that you can import a PDF into an FM document like an image, but I don't have much knowledge about pagination and all that stuff.

Russ