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

<< Prev | Next >>

> 16 Configuring DITA maps > 16.2 Configuring DITA ditamaps > 16.2.3 Accounting for missing topic levels

### 16.2.3 Accounting for missing topic levels

If your FrameMaker document uses a hierarchy of heading formats, such as:

Heading1

Heading2

Heading3

Heading4

And you have specified the following map levels for these headings (see §16.2.2 Specifying topic levels in ditamaps):

[DITAMapLevels]

Heading1 = 1

Heading2 = 2

Heading3 = 3

Heading4 = 4

But at least some of the time a heading is skipped in FrameMaker, such as:

Heading1

Heading2

Heading4

Wherever a Heading4 follows a Heading2, Mif2Go promotes that Heading4 to map level 3, because DITA does not allow skipped levels in a map. Additional instances of Heading4 that follow will remain at map level 4, and thus appear to be subordinate to the instance that was promoted to map level 3. How you adjust for this problem depends on whether a skipped level tends to be the rule or the exception in your FrameMaker document:

Heading3 present in most files

Heading3 absent from most files

Heading3 occasionally absent in a file.

Heading3 present in most files

If Heading3 is consistently present in most files and consistently missing in some, you would assign map level 4 to Heading4 in your project configuration file; and for each FrameMaker file where Heading3 is missing, include in the project directory a chapter-specific filename.ini that contains the following setting:

[DITAMapLevels]

Heading4 = 3

For example, if intro.fm has no instances of Heading3, include this setting in intro.ini. Mif2Go will use this setting as an override, for intro.fm only. See §33.1.1 Providing configuration files for individual chapters.

Heading3 absent from most files

If Heading3 is consistently missing from most files and consistently present in some, you would assign map level 3 to Heading4 in your project configuration file; and for the files that use Heading3, include in the project directory a chapter-specific filename.ini for each that contains the following settings:

[DITAMapLevels]

Heading3 = 3

Heading4 = 4

The setting for Heading4 will override the same setting in the project configuration file.

Heading3 occasionally absent in a file

If Heading3 is only occasionally missing in a file where it is usually present, you would have to use a Config marker to set the map level for Heading4 to 3 just before a group of Heading4s that are not subordinate to a Heading3, and another Config marker after the group to change the map level back to 4. See §33.2 Overriding settings with markers or macros.