14.4.3.2 Omitting element tags for selected paragraph formats
To specify that a particular FrameMaker paragraph format should not be mapped to any element:
When ParaFmt=No, tags for the format are omitted from output, leaving the text of the paragraph inside the enclosing element. Mif2Go assumes the paragraph contains PCDATA, and checks to ensure PCDATA is valid at the current point. If a paragraph format mapped to No has no text content, Mif2Go ignores it, checking to see if PCDATA is valid only if there really is some PCDATA. If PCDATA is not valid in the current enclosing element, and if closing current tags does not solve the problem, Mif2Go does not try to interpolate. Instead, Mif2Go puts out a "parent error". In this case it is your responsibility to map such a paragraph format to an appropriate element rather than to No. For example, if you have a figure anchor paragraph that also contains text, you would want to map its format to something allowable within <fig>, such as <desc>.
You can map formats to No for code examples (which can run on for pages), to avoid having each line of code mapped to a separate <codeblock> element:
In this example, specifying ancestry guarantees that Mif2Go will retain the original line breaks, instead of normalizing them as for HTML or XML. See §14.5.2 Designating DITA ancestor elements.
> 14 Producing DITA XML > 14.4 Configuring DITA elements > 14.4.3 Mapping paragraph formats to DITA elements > 14.4.3.2 Omitting element tags for selected paragraph formats