To specify that a particular paragraph format should not be mapped to any element:
[DITAParaTags] ParaFmt = No
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 §30.2.4 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.
DITA2Go 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, DITA2Go 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, DITA2Go does not try to interpolate. Instead, DITA2Go 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.See §30.2.6 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:
[DITAParaTags] Code* = No
[DITAParents] Code* = codeblock
In this example, specifying ancestry guarantees that DITA2Go will retain the original line breaks, instead of normalizing them as for HTML or XML. See §24.5.2 Designating DITA ancestor elements.