Mif2Go automatically generates bgcolor attributes for HTML tables based on table colors in FrameMaker. You can exclude these automatically generated attributes, while including any bgcolor attributes you specify in the configuration file or in a marker; see §23.4.7 .
Mif2Go uses the FrameMaker definition of row type to determine the extent of the table body, and not the configuration-file settings for heading/footing row counts you can specify with the [Tables] and [TableAccess] keywords described in §23.3.3 .
Where you have specified other colors for cells via Custom Ruling and Shading, those colors take precedence. Otherwise, if UseAltShading=No, and you defined alternate-row or alternate-column shading in a FrameMaker table, all body rows or columns of that table receive the color you specified for First on the Shading tab in Table Designer.
With the default setting, UseAltShading=No, if you specify the HTML bgcolor attribute for the <table> element, that background color applies to all cells. You can have Mif2Go apply whichever color is appropriate (which might be the alternate color if UseAltShading=Yes) in <tr> tags, as well as in cell tags:
UseRowColor specifies whether to use <tr> color attributes. When UseRowColor=Yes, Mif2Go applies cell <td> color attributes only when the cell color is different from the row color; this is a size optimization. Setting UseRowColor=Yes might affect the color of the spaces between cells. If UseAltShading=No, probably that color is determined by the page or table bgcolor value. However, Mif2Go ignores any value of bgcolor specified as a table attribute in the configuration file.
If you set UseRowColor=Yes, Mif2Go writes each table row using the color specified in your FrameMaker document (as modified by settings in [Colors]), provided that color is not "invisible", and has a tint greater than 1%. Then, Mif2Go puts out a background color for each cell, if the cell color or tint is different from the row color or tint. If you specify UseRowColor=Yes it does not really make sense to specify a table background color; it will always be overridden.
If UseRowColor=No, all rows are considered to be 100% white; Mif2Go writes out any cell-level colors or tints that are different from white. If UseRowColor=No, and you specify a table background color in HTML via bgcolor, you are likely to have trouble unless the table background color is white (#ffffff), in which case specifying it is redundant. If you have a cell where you want white, and you have a different table background color, you get the table background color in the cell instead, because in effect there is no cell background color.
See §23.2 for ways to specify a subset of tables.
Table fill colors are treated the same as text colors (see §12.6 ); the [Colors] mapping works the same way. Mif2Go specifies an HTML table background color and individual cell overrides as required, including using the correct heading/footing color for the cells in the table heading/footing rows. Choose colors and tints such that all the resulting colors are Web-safe. See §12.6.4 for more information.
You can use a table fill color that is just a tint. However, doing so might not give you Web-safe colors; a 100% tint of a distinct color is often a better idea. But not always; in one test case, a "highlight" color is applied (via Custom Ruling and Shading) to a set of columns, and shading is applied (via Table Designer) to alternate rows. What happens to cells that fall in both a shaded row and a highlighted column? If the alternate-row shading is a tint (for example, 50%) of the same color used for highlighting, the cells are tinted in the highlight color. But if the alternate-row shading is a different color, with 100% tint, these cells are not tinted; they are just highlighted, which looks a bit odd.