### 15.4.1 Understanding how Mif2Go delimits DITA elements

Mif2Go closes each element mapped from a FrameMaker paragraph format when a paragraph in that format ends. For example, even though a DITA list can be inside a <p> element, Mif2Go does not put it there; instead, the <sl> follows the <p>. Only elements that are marked as inline, including elements mapped from FrameMaker character formats, and inline images, are placed within a <p> element.

An interpolated block element stays open until Mif2Go encounters a paragraph that is not valid in that block.

Lists are identified by the FrameMaker format mapped to the list element it populates, such as <li> or <sli>; see §15.4.3 Mapping paragraph formats to DITA block elements, or by the parent of the mapped element; see §15.5.2 Designating DITA ancestor elements. Mif2Go provides the wrappers around the list items and around the whole list.

To minimize the need for markers in your FrameMaker document it is good practice to use distinct FrameMaker format names to identify different kinds of lists (List, Bulleted, Numbered, ParamTerm), body paragraphs (Body, Example), character formats (Strong, Emphasis), and so forth.

The easiest way to migrate and apply paragraph and character formatting from your FrameMaker document is to use the DITA outputclass attribute, which Mif2Go will set for you, to reference your current Framemaker formats or any others you map to those formats in [Classes]. See §15.4.6.6 Providing outputclass attributes for all elements.

| 15.4 Configuring DITA elements |  | 15.4.2 Treating FrameMaker format names as DITA element names |