§ Implementation specificities

• The encoding of an MDITA file is, by default, the system encoding (e.g. window-1252 on a Western PC).
  If you want to explicitly specify the encoding of an MDITA file, please save your file with a 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.
  

  The above example should work fine because ditac understands the GNU Emacs file variable called coding.
• When the ID of the MDITA topic is not explicitly specified (or specified as "???" like in the above template), the topic is automatically given an ID based on the basename⁽¹⁾ of the file containing it. Examples id="intro" if the MDITA topic is found in file "intro.md", id="Basic_Concepts" if found in "Basic Concepts.md".
• Adding a {.concept} class attribute to the title of an MDITA topic may be used to generate a DITA concept rather than a DITA topic.
• An internal link may be specified as [text](#TARGET_ID) or [text](#./TARGET_ID) or [text](#TOPIC_ID/TARGET_ID).
• Out of the box, ditac Markdown parser is configured to support the commonmark 0.28 “Markdown dialect” plus all the following extensions:
  • Abbreviations
  • Admonitions
  • Attributes
  • Definition lists
  • Footnotes
  • Ins
  • Strikethrough and subscript
  • Media tags
  • Superscript
  • Tables
  • Typographic characters
  • YAML front matter
  However, thanks to the flexmark-java software component used by ditac to implement Markdown support, all this can be configured by the means of -p load.mdita.XXX parameters. These load.mdita.XXX parameters are documented below.

§ Limitations

• Without a {.map} class attribute added to the title of an MDITA map, this map is confused with a topic.
• A link to another MDITA topic which is part of the same DITA document must be specified as [text](TOPIC_PATH#TOPIC_ID/TARGET_ID). Something like [text](TOPIC_PATH#TARGET_ID) or [text](TOPIC_PATH#./TARGET_ID) won’t work.

§ load.mdita.XXX parameters

-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

where abbreviation, admonition, attributes, etc, are all Markdown extensions, documented in Markdown extensions. This more or less corresponds to MDITA extended profile .

If, for example, you use the Github-flavored Markdown dialect, don’t need all the above Markdown extensions but need the autolink Markdown extension⁽²⁾ and also the task lists syntax extension. then pass:

• -p load.mdita.profile GITHUB
• -p load.mdita.extensions min
• -p load.mdita.autolink true
• -p load.mdita.gfm-tasklist true

Supported “Markdown dialects” are COMMONMARK, COMMONMARK_0_26, COMMONMARK_0_27, COMMONMARK_0_28, FIXED_INDENT, KRAMDOWN, MARKDOWN, GITHUB_DOC, GITHUB, MULTI_MARKDOWN, PEGDOWN, PEGDOWN_STRICT. See Markdown Processor Emulation .

none

No extensions.

min

Instructs ebookc to reset its extensions to the following minimal set of extensions:

• Strikethrough and subscript
• Superscript
• Tables
• YAML front matter

The above minimal set of extensions corresponds to what’s described in the Markdown Cheatsheet .

This also more or less corresponds to MDITA core profile .

most

Default value. See default extensions.