17.1.3 Understanding what information you must supply
You do not have to use structured FrameMaker to produce DocBook XML with Mif2Go. You can use structured FrameMaker, provided you use named formats rather than the Word-style formatting some structured-FrameMaker users prefer. Whether you use structured or unstructured FrameMaker, you must arrange the content of your document to fit the DocBook architecture before you can convert to completely valid DocBook output.
Mif2Go does not try to validate the output; you must use a validating parser to check output validity. However, Mif2Go does ensure valid parental relationships and first-child restrictions. Valid sequence of items within those constraints has to come from the implied or explicit structure of the FrameMaker document.
Mif2Go support for DocBook requires you to supply the following kinds of information in addition to your FrameMaker document:
Mif2Go provides two built-in configurations for content models for DocBook version 4.5: one for articles, and one for books.
If you need to modify one of these content models, you can download a copy from Omni Systems; see §32.2.1 Obtaining a copy of a built-in content-model. However, the only valid purpose for modifying a built-in content model would be to correct settings for element types. See §32.6 Inspecting and correcting element types.
To replace a content model, use free command-line utility dtd2ini to generate a content model from another DTD, and produce a content-model configuration file for your DocBook project. See §32.2.2 Generating a content model from a DTD.
You must map FrameMaker file information, such as formats, to DocBook elements. This information goes into configuration file m2docbook.ini, and possibly into chapter-specific configuration files. You might have to use marker in your FrameMaker document to provide information such as topic IDs, element names, and attributes, in cases where these items cannot be derived from the document.
Note: The name of your FrameMaker book must not duplicate the name of any chapter file.
In an unstructured FrameMaker document, presentation might be the same for several different usages. Mif2Go cannot necessarily determine whether (for example) text tagged <Italic> is a computer term, a foreign language term, or a long quote, all of which have different representations in DocBook, based on the context. The onus is on the author to disambiguate these usages, if necessary by inserting DocBook-specific custom markers in individual instances of particular formats. Mif2Go does handle a few presentational features automatically; for example, by default forced returns (FrameMaker Shift+Enter) are converted to spaces.
> 17 Converting to DocBook XML > 17.1 Generating DocBook XML with Mif2Go > 17.1.3 Understanding what information you must supply