🚀 go-pugleaf

I believe there's more to it than that. (I'm researching the same problem while single-sourcing via FrameMaker-WWP-HTML Help...)

I believe I've eliminated the general technique of (1) Overlaying a graphic contained in an Anchored Frame with one or more text frames, then (2) In the text frame or frames, creating Hypertext links to named Hypertext destinations.

I've verified that this technique works great if one is outputting to PDF, but does not appear to work for content exported to HTML. This seems to be because, regardless of whether or not WebWorks Publisher (WWP) is used, the resulting HTML doesn't receive any of the requisite image mapping information. This despite Quadralay's claim, in WWP Pro 7's User Guide (or OLH) under "Defining Imagemaps", that such a thing is possible.

The best hope I've found so far is a 12-step procedure (please, no 12-step jokes) on pages 558-559 of "FrameMaker 7: The Complete Reference," by O'Keefe and Loring. This procedure involves a somewhat clumsy technique that involves creating shape-specific text frames on reference pages, creating flow tags, and entering stacked Hypertext tags on the body pages. Even if this technique will work (I haven't tried it yet) it looks ugly at first glance and probably won't be fun to implement if one has a lot of image mapped graphics to export to HTML. I hope there's a more straightforward way out of this problem.

In the meantime, I second the question: Does anyone know a clean, relatively straightforward, way to export image mapped graphics from FrameMaker to HTML? Moreover, will the techique work "cleanly" for both PDF and HTML output? (I.e., one won't be obliged to create and maintain two images, one mapped for output to PDF and one mapped for output to HTML...)

Cheers (and y'all have a great weekend),
Riley