23.4.4 Using referenced, embedded, and compound graphics
Suppose your FrameMaker document includes all of the following:
• Original referenced graphics (GIFs, for example) that do not need to be converted
• Embedded graphics that must be exported
• Compound graphics: images in anchored frames that include callouts or other drawing elements created in FrameMaker.
Mif2Go undertakes two distinct operations:
1. Mif2Go generates graphics files for all anchored frames. This is an all-or-nothing operation, which is required if a document contains any graphics with callouts.
2. Mif2Go writes the HTML files. This operation does not have to use the graphics produced in Step 1.
To have Mif2Go use the original referenced graphics—except for those with callouts—you would set the following option:
Whenever you have a referenced graphic, and it is alone in its frame (no callouts, title, second image, and so on, in the frame), the resulting HTML uses that graphic. For all other cases the resulting HTML uses the graphics Mif2Go generates from your document.
To have Mif2Go export embedded graphics (those without callouts) to files of their own, you would set the following option:
The exported files are referenced in the resulting HTML just as though they had been referenced in FrameMaker in the first place. See §31.2.3 Exporting and converting embedded graphics for information about the appropriate export settings to use.
Graphics that include callouts or other elements created in FrameMaker must be processed with FrameMaker export filters; see §5.7.2.2 Using FrameMaker graphic export filters. The only other option would be to use a third-party graphics program to add the callouts to the original graphic. If any compound graphics include images imported into FrameMaker at a resolution other than 96 DPI, you would need to scale the graphics on export; see §23.9 Scaling images for HTML.
> 23 Including graphics in HTML > 23.4 Specifying options for HTML graphics > 23.4.4 Using referenced, embedded, and compound graphics