Marsha,
I have done some testing (using FM 7.2, but table handling did not
change from 7.1 to 7.2) with several variations of the model you describe.
As I suspected, the problem seems to involve use of the element names from
the CALS table model. In particular, the CALS table model is a five
Marsha,
I have done some testing (using FM 7.2, but table handling did not
change from 7.1 to 7.2) with several variations of the model you describe.
As I suspected, the problem seems to involve use of the element names from
the CALS table model. In particular, the CALS table model is a five
Marsha,
Do you have a r/w write rule that maps the tgroup element to a table? Is
the TCaption element declared in your DTD and defined in the EDD to a
FrameMaker table title? FM does treat an element named "tgroup" specially;
it tries to interpret it in light of the CALS table model, and your
Marsha,
Do you have a r/w write rule that maps the tgroup element to a table? Is
the TCaption element declared in your DTD and defined in the EDD to a
FrameMaker table title? FM does treat an element named "tgroup" specially;
it tries to interpret it in light of the CALS table model, and your
I'm working on converting some files that were created with DTD "A" to
DTD "B". I have **almost** everything working. The XML files were not
originally created with FrameMaker.
I can now open them in FrameMaker with no errors and the structure is
exactly as I defined it. However, when I save the X
I'm working on converting some files that were created with DTD "A" to
DTD "B". I have **almost** everything working. The XML files were not
originally created with FrameMaker.
I can now open them in FrameMaker with no errors and the structure is
exactly as I defined it. However, when I save the X