Word tables are constructed differently from FrameMaker tables, and converted tables might not look quite the same in Word. For example, titles of tables that span all columns and sideheads in FrameMaker might not line up with the left edge of the table in Word. And multiple table header rows might be split across page boundaries.
To prevent table titles from being separated from their tables across Word page boundaries, and to keep header rows together, in FrameMaker set Keep With: Next Pgf for all table-title and table-header paragraph formats.
For other differences you might have to supply a conversion template (see §2.4 ), or modify table formats in your FrameMaker document:
If you use conditional text to hide all the rows in a table (but not the table anchor), you will see extra space in the RTF output where the table would have been displayed. To avoid this space, be sure to hide the table anchor.
FrameMaker allows a graphic to overflow its table cell, and overlap cells to the right; Word does not. If your document has tables that contain graphics, make sure any cells under the graphics are straddled.
If your FrameMaker table format includes a space-below value greater than zero, Mif2Go adds a blank "spacer" paragraph after the table in the RTF output, because Word has no way to represent the space-below feature of a FrameMaker table.
Word 9/2000 and earlier versions cannot handle rotated table cells, unless you put the content of each cell in an anchored frame and rotate it inside the frame. The text will appear correctly in Word unless you try to edit the picture created from the anchored frame; then Word remembers that it cannot rotate text, and unrotates everything. Word 10/XP does allow rotated text in selected table cells, but does not allow rotation of a whole table.
Given the opportunity, Word handles table cells that straddle columns by combining the cells involved in the straddle into a single cell. Because this might not be what you want in Word output, by default Mif2Go does not combine the cells; however, you can override the default. To combine column-straddling cells into a single cell:
For WinHelp output, the default value of MergeStradCells is Yes (the opposite of the default for Word); see §7.4.2 .
Word seems incapable of handling tables that have more than 63 columns. Such a table ends up in Word with all columns beyond the 63rd merged into the last column allowed, making that cell much taller than the rest, in every row. As a workaround, you can save the FrameMaker file that contains the table as plain text, with tab delimiters for the table cells and hard returns for the rows. Discard everything in the resulting.txt file except the table, and import the file into Excel. Select all columns, resize their widths if necessary, and print to PDF, reducing the size if necessary. Then import the PDF into Word.
> 5 Converting to print RTF > 5.11 Converting tables to print RTF