Re: Problems in FM to XML conversion

[Pamel...@adobeforums.com]

=========================================================
Structured FrameMaker 7.2p158
Windows XP Professional 7.0.0 12/14/2004 Service Pack 2
=========================================================

I've been told that there are lots of errors in the Developer Guide.
I've tried using their examples as well as some examples in the xml cookbook but neither seem to work.

I'm trying to convert an Epic XML file (which uses the cals.dtd) to structured FrameMaker (for which I have created an EDD “OLLD_EDD.fm” using the 050512navseac2.dtd). I thought I ould do this by using the read write rules but have come across some problems where it seems that the read write rules are being ignored.

The Epic Editor generated XML file uses the DTD “cals.dtd” and and edited version of the STYLESHEET “cals.fosi”.

The 050512navseac2.dtd(OLLD) is very similar to the cals.dtd with just a few differences (the root element for the cals is “doc” while the root element for the olld is “docnavy-etm”; the “docno” is wrapped in “tmidno” in the cals, while “tmidno” doesn’t exist in the olld; “volnum?, revnum?, doctype, maintlvl*, prtitle, stitle?” are not wrapped in the cals, but they are wrapped in “titleblk” in olld).

Using the “structapps” from the “C:\Program Files\Adobe\FrameMaker7.2\Structure” folder, I added an application for “OLLD” (using the xdocbook application for a template).

I used the “rules” file from the “C:\Program Files\Adobe\FrameMaker7.2\Structure\xml\xdocbook\app” folder and named it “OLLD_RW_Rules.rw”. I then tried to modify it and took everything out but a few items to test it.

The “
I ended up having to go into the FM file and deleting and changing some of the elements so that it would work with our OLLD.DTD and OLLD_EDD. We also had to split them up into the separate book files because the Read/Write Rules wouldn't do that either.

I'm looking to find a way to automate this process (to get the read write rules to work—or maybe set up a mapping file instead or in addition to?). [more info in next entry]

[Pamel...@adobeforums.com]

continued
===============
In the couple of versions I tried, what resulted from the import of the xml seems to not have read the write rules as it didn't work (for olld application in the structapps.fm). The elements attict, timidno and the others that show up in red are still there instead of being "drop"ped. The "authnot" didn't get renamed to "notice".

I had to go thru the xml file and do a find/replace on the "boardno" and change it to "entityref" to get the graphics to come into FM. I need to figure out how to get the read write rules to do this for me on import and then in reverse to go from the FM back to xml. There were some other attributes for the graphics in the dtd that need converted/mapped/renamed for FM and then in reverse.

I'm trying to convert (cals.dtd) xml file to FrameMaker file (olld.dtd). The 2 dtd's are similar except for a couple of differences..so I was trying to use the read write rules to rename them.

I had found a file that is supposed to help you write the read write rules in frame but I'm not quite sure about some of the syntax. It still just doesn't seem quite right...it had seemed to say that you could put in an attribute without the element but in an example with the online documents, it showed that it should be in more of a subrule...the Frame file said to just the first, but the example said to use the whole part surrounding it ...

==========[frame]================
entity attribute "boardno" is fm attribute "entityref";

===========[book example]==============

element "graphic"
{
is fm graphic element "graphic";
entity attribute "boardno" is fm attribute "entityref";
}
==================[another book example]============
element "graphic"
{
is fm graphic element "graphic";
attribute "graphatt"
{
is fm property entity;
is fm attribute;
}

====================================================
here's what I'm thinking it should look like, but not sure of what all of them should be and I'm not sure which example above to follow...can someone please help??

attribute "graphsty" is fm attribute "graphsty";
attribute "llcordra" drop;
attribute "rucordra" drop;
attribute "reprowid" is fm attribute "reprowid";
attribute "reprodep" is fm attribute "reprodep";
attribute "hscale" drop;
attribute "vscale" drop;
attribute "scalefit" drop;
attribute "hplace" drop;
attribute "vplace" drop;
attribute "coordst" drop;
attribute "coordend" drop;
attribute "rotation" drop;
attribute "%secur" drop;

==============
Here are the original definitions in the dtd:

[Pamel...@adobeforums.com]

continued
===============

[anand...@adobeforums.com]

Hi Martti,

Thanks. Should there be any mention of Colspec in my EDD? I dont find it in mine. Could that be a problem?

When should I write an API client? Would there be a need to write one for converting FM to XML?

Regards,
Anand

[Pamel...@adobeforums.com]

let me try that again...

Here are the original definitions in the dtd:

==============================================
Element (Container): figure
General rule: title?, (graphic | (subfig | subfoldout)+)
Automatic insertions
Automatically insert child: graphic
==============================================

Element (Graphic): graphic
Attribute list
Name: boardno String Required
Name: graphsty Choice Optional
Choices: inline | outline | both
Default: outline
Name: reprowid String Optional
Name: reprodep String Optional
Name: scalefit Choice Optional
Choices: 0 | 1
Initial graphic element format
In all contexts.
Insert anchored frame.

[kalpana...@gmail.com]

Informatics Outsourcing is an Offshore Data Management service company. Data Management Service includes all types of Data Conversion, File Conversion, XML Conversion, HTML Conversion,SGML Conversion, Document Conversion,Data Entry, Data Extraction and Validation,OCR and ICR Services with affordable price. Our team to give the solution quickly and given requirements.