When you use Mif2Go "out of the box" to generate HTML, without setting graphics options, the graphics from your document might look quite different from the way they look when you "Save as" HTML directly from FrameMaker. Differences can appear in any of the following:
Screen captures might be unreadable with "out-of-the-box" options. By default, Mif2Go retains the image size specified in your FrameMaker document. However, when you "Save as" HTML, FrameMaker produces the graphics unscaled. To do the same with Mif2Go, set the following option:
See §22.9.2 .
By default, Mif2Go retains the alignment used in your FrameMaker document. However, when you "Save as" HTML, FrameMaker produces HTML with images all left aligned. To mimic FrameMaker HTML image alignment behavior with Mif2Go, set the following option:
See §22.6.2 .
Graphics formats that work best in FrameMaker for printed documents generally are not those that work well on the Web. If some of the graphics in your FrameMaker document are not in an appropriate format, or are not alone in their frames, you will have to convert them.
If a graphics file imported into or exported from your document is in a format other than JPEG, GIF, or PNG, and you do not specify how it should be converted or mapped, Mif2Go plunks the name of the graphics file into the HTML output file and lets the browser sort it out later. In some cases, this might work. For example, Microsoft Internet Explorer can display BMP and WMF graphics with no problem.
> 22 Including graphics in HTML > 22.2 Understanding graphics processing for HTML