Omni Systems, Inc. Mif2Go User's Guide, Version 55
> 15 Converting to DITA XML > 15.4 Configuring DITA elements > 15.4.3 Mapping paragraph formats to DITA block elements > 15.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. Compare this setting with the
effect of the NoPara
format property; see §21.3.6 Stripping paragraph properties.
The ParaFmt
=No
setting is similar, but for DITA output it is recognized in places where
the NoPara
property is not. If you do not get
the correct result with one, try the other.
Mif2Go assumes a paragraph mapped to No
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
.
Delete paragraphs with unwanted text
If an instance of a paragraph format mapped to
No
contains text, and PCDATA
is not valid in the current enclosing element, then if closing current
tags does not solve the problem, Mif2Go does not try to interpolate. Instead, Mif2Go issues 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>
. If you do not want the
text to appear in DITA output, instead of mapping the paragraph format
to No in [DITAParaTags]
, mark the format for
deletion. For example:
See §21.3.12 Eliminating unwanted paragraphs.
Map code- example formats to No
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 §15.5.2 Designating DITA ancestor elements.