How to import from / export to multiple flows

[_Conrad_Christian_]

Hi all,

we have developed an FM unstructured template where each page contains basically two text boxes: a main text box where all the content goes (main flow), and an info text box where specific page-related information goes (info flow(s)).

Now, we want to make a Structured FrameMaker application out of it. My question is: Is there a way to direct XML content into a particular flow, depending on the elements (or whatever)?

I may add a question which is kind of off-topic from the above, but also not: How can I deal with the FM built-in line, circle, ... graphics in an structured application? I mean, how can I export and import them? I have no read/write rules found supporting these types of objects. If I have to write an import/export api client, how does FrameMaker behave when inserting a new line? I mean, how is the Structure View informed to do an update (knowing that my drawn line is a "line" element inside the structure tree with appropriate attributes)?

BR,
Conrad

[Russ Ward]

Conrad,

For your first question, there is no way to import XML into different flows unless you write a custom import/export client. When importing XML, it comes into the main flow only. If you stop to consider the endless myriad of possibilities with other flows, you'll understand why the original software architects chose this simplified route.

For FM drawing objects, I'm not sure. I think that maybe you can set them up (r/w rules) to save as MIF files, so they will come back in the same as they left. Otherwise, saving as XML will cause them to be rasterized into a single graphic. I don't personally use the FM drawing tools so someone else with more experience would have to address the validity of what I just said.

For your other questions, I'm not quite able to follow what you are asking.

Russ

[_Conrad_Christian_1]

Russ,

Thank you for your reply. So your answer confirms what I supposed after going through all the documentation. Probably, we will just keep to .FM format, because actually we do not need XML as source. This will keep things easy - and we can avoid an import/export client.

But the problem with multiple flows is also: you may mix unstructured and structured flows in a document, and "Validate" will not complain. So we have to set up our "own" validation to guarantee 100% structured flows.

The other questions: It was about the FM drawing objects, if there is a representation for EDD or read/write rules. But based on my research, I think there is no such representation, as it is e.g. for anchored frames (you click on an anchored frame and the corresponding element in the structure view is highlighted and vice versa).

Best regards,
Conrad

[Russ Ward]

Conrad, you are correct, there is no corresponding representation for drawing objects. What goes on inside an anchored frame is beyond the visibility of the structural markup. Note, however, you could put a text frame inside an anchored frame whose content could contain its own structure tree.

Russ