Conversion table adds empty rows to table

Question

Hi,

I try to convert a table to structured FrameMaker that contains several paragraphs in a single cell. FrameMaker successfully converts the table but adds empty rows beneath the row containing the cell with multiple paragraphs in it.

The empty rows cannot be removed or changed.

Can anyone help me with this?

Below a screenshot.

Regards, Arnold

Lynne A. Price · Accepted Answer

Arnold,

Does your screen shot show the original unstructured document or the structured document produced with the conversion table?

I suspect that the fact that there are multiple paragraphs in a cell in the row preceding the mystery rows is irrelevant.

Note that there are no cells in these rows. My guess is that there are indeed three invisible rows in this table, but that each cell in the row with the multi-paragraph cell straddles all the cells in its column. To confirm, click in one of the cells in the row with the multi-paragraph cell and look at the commands on the Table menu. Does it include Straddle or Unstraddle? If Straddle, then my theory is wrong!. If it shows Unstraddle, select that menu item. The empty rows should now show cells in the Structure View and you should be able to delete them.

--Lynne

ScottPrentice · Answer

Yeah .. that's a bit of a bugger. I'd love to hear if someone has a good solution for this (or at least a reasonable explanation).

I will see that sometimes when the table has conditions on rows or cells, or when there are row/cell spans (or even maybe if there were spans that have been merged?). Sometimes it makes sense, and other times I'm at a loss for why it happens. No, you can't delete those via the UI, and if I recall correctly, you can't do it via the API either.

If you're converting to XML, you'll be able to fix it once it's been exported to XML (as long as it doesn't crash on the way out .. which can happen if the model isn't valid .. and this is often a case where the model is invalid). If you're not converting to XML, you typically have to fix this manually by creating a new clean table and copy/pasting the "good" rows into it, then deleting the old table. You might be able to fix it in MIF (export to MIF, clean it up .. if you know what you're doing .. then open the MIF back in FM).

That's all I've got. Other ideas?

Cheers,

...scott

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded