Navigation Bar for Support Home Products Order Support Download Links About Contact
[spacer]

Support

Technical Support

Documentation

Single Sourcing

FrameMaker MIF to RTF

A Better RTF Generator

WinHelp Support Features

Starting a Help Topic

Keywords, Jumps, and Popups

Conditional Text and Modified Formats

Graphics and Special Characters

More RTF Customization

Advantages over Frame 5 RTF Filter

Support and Enhancements

Compiling WinHelp

HTML Production

Site Map

Contact Us

FrameMaker MIF to RTF

Advantages over Frame RTF Filter

Now that you’ve read how we support WinHelp, let’s compare that to the way Frame supports it with the built-in RTF filter. We think you will agree that there’s substantial added value here. The main point: we do the hard work for you, so transparently that you can easily support your WinHelp needs using the very same files you use for the print docs.

WinHelp Support

WinHelp Feature

Frame RTF Filter

Mif2Go RTF Filter

Topic start

Create special footnotes by setting a custom footnote sequence, then typing in the contents for each footnote.

Add the existing character or paragraph format name to the mif2rtf.ini file, or apply a character tag to the heading.

Jumps

Apply underline format to jump text, then add reference text manually.

Use Frame hypertext markers and cross-references normally. Or apply a character tag (need not have any visible effect); the reference is generated automatically.

References

References (context strings) are typed in as conditional text. That is, all conditional text becomes context strings, and is not usable in any other way.

Most references are generated automatically; character tags and markers are used where needed. Conditional text remains available for its normal purposes.

Contents

No support for .cnt file.

Creates .cnt file containing topics and mid-topic jumps at the levels you specify.

Keywords

Keywords are typed in as index markers. Adding additional keyword sequences (as “A” footnotes) or WinHelp-only keywords (as “K” footnotes) conflicts with the topic start footnote method, and cannot be done.

Index markers converted automatically. Added keywords supported by tagging and by custom markers; unlimited added keyword sequences are available.

Graphics

Internal graphics are not supported. If an imported graphic has a WMF facet, it converts to an internal WMF graphic in RTF.

Frame internal graphics are converted to external WMFs, with references put into the RTF file. External graphics are also referenced in place.

Fonts

Change manually as needed.

All mapped in dwrtf.ini file.

Quotes and dashes

Change manually to the forms supported in WinHelp (straight quotes, etc.).

All converted to WinHelp-usable closest equivalent automatically.

Sub and superscript

Not supported.

Automatically generates external WMFs with inline references.

Bullets

Not supported; Dingbats become text.

Bullets and Dingbats all become in-line references to the bullet.bmp file.

Hypertext

Not supported.

Automatically converts gotolink and openlink as jumps to matching newlink. Makes alertboxes into popups.

Equations

Not supported.

Supported for FM 5.5 or later, when using Mif2Go within FrameMaker.

Page breaks

Required after topics and popups, must be removed anywhere else.

Existing page breaks are ignored; those required for topics and popups are generated automatically.

 
Google


Search WWW Search www.omsys.com

Made with Mif2GoMif2Go