Omni Systems, Inc.

  

Mif2Go User's Guide, Version 55

  

Valid HTML 4.01!

 

Made with Mif2Go

6 Converting to print RTF > 6.1 Converting to Word: a one-way street > 6.1.4 Migrating a document from FrameMaker to Word


6.1.4 Migrating a document from FrameMaker to Word

If you plan to maintain your document in Word instead of in FrameMaker, the transition is not simple. Numerous FrameMaker features that Mif2Go emulates in Word, such as sideheads, are not maintainable in Word; see§6.1.1 Understanding differences in implementation.

Mif2Go can convert numbering to an active form for Word, but not to the numbering Word normally uses. Instead Mif2Go creates SEQ fields; see §6.7.5 Converting autonumbered formats. This is because Word normal numbering is notorious for failing in large files, requiring hours of work to recreate. Although the SEQ fields are stable, you must copy/paste them into new paragraphs that you create.

TOC generation in Word is entirely different from TOC generation in FrameMaker. A Word TOC depends on fixed style names Heading1 through Heading9. You would have to map the FrameMaker paragraph formats that you want included in the TOC to one of those heading styles. And of course Word knows nothing about FrameMaker options for formatting a TOC.

Migrating from FrameMaker to Word has a very high price. Make sure you are willing to pay (and pay, and pay) before you go down that hard road.



6 Converting to print RTF > 6.1 Converting to Word: a one-way street > 6.1.4 Migrating a document from FrameMaker to Word