8.9.9.2 Using text insets for both pop-ups and normal topics
To use the same content for both a normal topic and a pop-up, without duplicating text:
1. Create a new FrameMaker file, for example, Popups.fm, and include this file in your FrameMaker book.
2. Place each pop-up content chunk in a new tagged flow in Popups.fm, keeping the original paragraph format name; for example, Head2. You must give each flow tag a name; perhaps the same name as the identifier in the newlink marker for the pop-up. (Flow tag names are not restricted to single letters.)
3. Import each pop-up text inset into main text flow A in Popups.fm. Yes, you can do this, even if the insets are stored in the same file!
4. For each pop-up, do the following:
4.1. Go to the pop-up text in its own named flow in Popups.fm, and cut the hypertext newlink marker.
4.2. Go back to main flow A in Popups.fm, and paste the marker just before the head of the inset for that pop-up, in the same paragraph.
4.3. Go to the place in the original FrameMaker file where the pop-up content was located, and replace that text with another import-by-reference of the pop-up from its own flow in Popups.fm. This time you do not want the hypertext newlink marker, and it will not be present.
5. Create a new configuration file, Popups.ini, that contains only the following setting (and any comments you want):
Head2=Topic Scroll NoXScroll NoTitle
This ensures that when Mif2Go processes Popups.fm, you get the pop-up properties rather than the normal content properties for paragraph format Head2. You do not need an entry for Head2 in _m2winhelp.ini.
The advantage of this method is simplified maintenance. You edit the pop-up content in only one place: its own text flow in Popups.fm.
> 8 Generating WinHelp > 8.9 Creating jumps and pop-ups for WinHelp > 8.9.9 Using the same content for both normal topics and pop-ups > 8.9.9.2 Using text insets for both pop-ups and normal topics