Hello,
I currently have about 150 pages fm file, which were orginally unstructured but I managed to make a working structure to it. It has mainly tables, which have crossreferences, images, graphics, inner tables and stuff, so about normal technical document. Reason why I'm structuring it and turning to XML is that we have some other XML file from where we will add data to this document and currently that is done by hand and we want to do it my machine. Those things are done by magic of programmers who can speak better c-related languages than English.
I can make XML from this fine, so that XML that is created is valid and structure looks like it is copied fine to XML. Inner tables, images and graphics are currently inside anchored frames as graphics elements, since they were something similar in unstructured document and read/write rules transform them to EPS images, since inner tables don't work as SVG, which I would otherwise prefer, because it is also XML and those anchored frames have some crossreference links to document's other parts. SVG would be also easier to handle in programming (or so I think) than EPS. If anyone can think better way to do these, I'm open for suggestions.
Issue currently is that when I open this created XML in FrameMaker, it first loads about half an hour (computer is Intel T2500 2GHz, 2GB RAM, XP Pro SP3 laptop and FM is version 10) and then shows 9 pages of error logs about "framemaker cannot insert the table cell (Cell) at the current position" and then document is shown as 600 to 1000 pages "masterpiece" where first 150 pages looks normal but after that first page is shown again and tables are shown like one column in page. One would suggest that if file is created by FrameMaker, FrameMaker would open it normally, but apparently that is not the case.
Read/write -rules look currently like this: (if it helps at all)
element "Table" {
is fm table element "Table";
}
element "TableHead" {
is fm table heading element "TableHead";
}
element "TableBody" {
is fm table body element "TableBody";
}
element "Row" {
is fm table row element "Row";
}
element "Cell" {
is fm table cell element "Cell";
}
element "HRef" is fm cross-reference element "HRef";
element "Row" {
is fm table row element "ROW";
}
element "Cell" is fm table cell element "CELL";
element "Graphic" {
is fm graphic element;
writer anchored frame {
export to file "$(entity).eps" as "EPS";
specify size in pt;
}
}
element "Equation" {
is fm equation element;
writer equation export to file "$(entity).eps" as "EPS";
}
There are some things that might look weird for some people. There are some conditional text in FM file and without rules like
element "Cell" is fm table cell element "CELL";
XML wouldn't be valid against DTD.
I would appreciate any help. I can also provide some other files here, but due NDA reasons, real document is No-Go, but I think if structure is needed to see, DTD is fine.