While working with Structured FrameMaker, I've collided with FM 7.2's apparent unwillingness to create a new structured book file...(?)
I began with a properly validating structured chapter file that I wanted to put into a new book. So I used File > New > Book to create the new book and automatically add the chapter file to it.
At that point the new book would not validate. Instead, I received the error message "NoName: Element is undefined".
Things went downhill from there. I figured out that I could use structured view of the of book to unwrap the book from the red "NoName" element. But doing that meant that anytime I tried to add a file to the new book, FrameMaker immediately crashed hard.
A co-worker then fixed the problem by copying an existing structured book, using Save As to save the book under a new name, deleting the renamed book's chapter files, and finally adding the desired chapter file or files to the new book.
This seems so insanely convoluted that I'm sure there must be some more sensible way. (It also raises the chicken-and-egg question of where did that seminal structured book file come from? Please -- no creationists versus evolutionist arguments here...)
Yet I can't readily identify that way -- anytime I try to create a new book, FM 7.2 seems to be creating an unstructured one. Any menu-based method I try for creating a new empty book produces the same "NoName..." error message.
So, can someone please tell me what I'm seeing and how I can remedy it?
Cheers & thanks,
Riley
I began with a properly validating structured chapter file that I wanted to put into a new book. So I used File > New > Book to create the new book and automatically add the chapter file to it.
At that point the new book would not validate. Instead, I received the error message "NoName: Element is undefined".
Things went downhill from there. I figured out that I could use structured view of the of book to unwrap the book from the red "NoName" element. But doing that meant that anytime I tried to add a file to the new book, FrameMaker immediately crashed hard.
A co-worker then fixed the problem by copying an existing structured book, using Save As to save the book under a new name, deleting the renamed book's chapter files, and finally adding the desired chapter file or files to the new book.
This seems so insanely convoluted that I'm sure there must be some more sensible way. (It also raises the chicken-and-egg question of where did that seminal structured book file come from? Please -- no creationists versus evolutionist arguments here...)
Yet I can't readily identify that way -- anytime I try to create a new book, FM 7.2 seems to be creating an unstructured one. Any menu-based method I try for creating a new empty book produces the same "NoName..." error message.
So, can someone please tell me what I'm seeing and how I can remedy it?
Cheers & thanks,
Riley