Omni Systems, Inc. Mif2Go User's Guide, Version 55

<< Prev | Next >>

> 14 Converting to generic XML > 14.2 Setting up a generic XML project

## 14.2 Setting up a generic XML project

For the most part Mif2Go conversions to XML employ the same project set-up options, conversion methods, macros, and configuration settings as conversions to HTML or XHTML; see §13.2 Setting up an HTML project.

Set-up options

If you are using the FrameMaker plug-in version of Mif2Go, you get the same Set Up dialog for XML as for HTML; see §13.2.2 Choosing set-up options for an HTML or XHTML project.

Conversion files

The same conversion files are generated and named the same way for XML as for HTML or XHTML; see §C.2.3.2 HTML/XML conversion files.

Default settings

Default values for configuration settings are the same for XML as for XHTML, with the following exceptions:

Section | Keyword | XML default | XHTML default
[CSS] | ClassIsTag | Yes | No
[Graphics] | GraphScale | No | Yes
[HTMLOptions] | AlignAttributes | No | Yes
AllowOverrides | No | Yes
Footnotes | Inline | Jump
NoFonts | Yes | No
UseAnums | No | Yes (except lists)
UseFootXrefTag | Yes | No
UseHeadAndBody | No | Yes
XMLRoot | doc | html
[Tables] | UseCALSModel | Yes | No
| CellAlignAttributes | No | Yes
| CellColorAttributes | No | Yes
| TableAttributes | No | Yes

Generated files

Converting FrameMaker-generated files is the same process for XML as for HTML; see §13.8 Converting generated files for HTML. However, you can also produce an XML-tagged index directly from FrameMaker index markers; see §14.8 Converting index entries to generic XML.

Markers and macros

If you are converting an unstructured document, you can use markers and Mif2Go macros to introduce structure; see §29 Working with FrameMaker markers and §28 Working with macros.