XMLmind DITA Converter fully supports MDITA  , which specifies how to write DITA topics and maps in Markdown
, which specifies how to write DITA topics and maps in Markdown  .
.
 :
:--- id: ??? --- # Topic title here Short description here. Topic body starts here.
 :
:# Map title here {.map}
   
- [???](???)
  - [???](???)
  - [???](???)
- [???](???)
            {.map} class attribute added to the title of the map. Without it, the above template would be
               translated to a DITA topic.window-1252 on a Western PC).UTF-8 or UTF-16 BOM (Byte Order Mark) or add an encoding directive inside a comment anywhere at the beginning of your file. Example:<!-- -*- coding: iso-8859-1 -*- --> Heading ======= ## Sub-heading Paragraphs are separated by a blank line.
 called
 called coding.{.concept} class attribute to the title of an MDITA topic may be used to generate a DITA concept rather
                        than a DITA topic.-p load.mdita.XXX parameters. These load.mdita.XXX parameters are documented below.{.map} class attribute added to the title of an MDITA map, this map is confused with a topic.load.mdita.XXX parameters-p load.mdita.extended-profile true is implicitely passed to ditac. This parameter is simply a shorthand for:-p load.mdita.abbreviation true -p load.mdita.admonition true -p load.mdita.attributes true -p load.mdita.definition true -p load.mdita.footnotes true -p load.mdita.gfm-strikethrough true -p load.mdita.ins true -p load.mdita.superscript true -p load.mdita.tables true -p load.mdita.typographic true -p load.mdita.yaml-front-matter true
autolink Markdown extension(1), then pass:-p load.mdita.core-profile true -p load.mdita.autolink true
ditac.-p load.mdita.core-profile true is simply a shorthand for:-p load.mdita.gfm-strikethrough true -p load.mdita.superscript true -p load.mdita.tables true -p load.mdita.yaml-front-matter true
‣ Parent topic: Appendix B. Lightweight DITA support
| (1) | Turns plain text URLs and email addresses into <xref href="...">elements. |