🚀 go-pugleaf

Hi Shelley,

I don't have a good answer for you, but I wanted to at least let you know that you aren't alone in your assessment. The clunky relationship between FM books and XML roundtripping probably has its roots in the fact that there really is no such thing as a "book" in XML, so the engineers of FM chose a certain way to sort of mimic it. In my work, I've found it better to simply avoid the whole book thing in XML, dealing with XML at the file level only. This has required some customization of FM, though, to regain the book structure (along with the book benefits) once back in FM.

If I were more inclined to fuss with the book during roundtripping, I might have figured something else out and could be more helpful to you. I'm sorry that I am not.

Russ

Russ,

Thanks (I guess!) for your reply, although it's certainly not what I wanted to hear.

So given the opportunities to control roundtripping through either XSLT, the FDK, or a client API, would there be a way to:

* Save book as XML, which generates various entities and files based on the chapters' names
* Open the XML book in Frame and have it RETAIN the names of the entity files in Frame rather than using the generic "chapter1", "chapter2" etc.
* Resave said book as XML so that it retains the same entity names
* And so on.

The main take-home point being to retain the same names each time.

And if not, would you mind sharing (briefly)your own workflow w/o using a book-level file?

Thanks in advance,
Shelley

Hi Shelley,

In my dealings with FM/XML, I use XML files like FM documents, authoring and saving them like FM binary files, checking in/out of source control individually, etc. These files are always intended to be chapters of some publication down the road, so the FM book concept is still an important part of being able to effectively publish. The problem with this, though, is that FM does not handle non-FM files in a book very well. You can get some things to work such as chapter and page numbering, but it is clunky and time-consuming every time you want to do it. So, when I need to publish, I have an API client which basically converts the XML files to FM to make a "throwaway" book, used just for making a PDF or whatever.

The process of converting an XML-file book to FM files is fairly straight-forward if you work with the API or FrameScript. It really only takes a couple of steps per file:

- Save as FM binary
- Adjust all cross-reference file targets, replacing the *.xml extension with *.fm

Note that this workflow assumes that the "book" concept is only useful to you in FrameMaker... if you need the higher-level book container in XML, you'd need to do something a little different.

This is certainly a home-made type of workflow and I don't know that it would be useful to you or not. I just brought it up because I've come to work this way due to dissatisfaction with FM books and XML. I saw on the Yahoo forum that you got some good advice, hopefully somewhere between here and there you can get something working.

Russ