anchor.diff:  Video and audio elements are not supported.
   See https://github.com/bytesparadise/libasciidoc/issues/677[Issue #677].
   
  -== File Inclusions
  -
  -File inclusions are performed before the full parsing takes place. During this phase, the parser looks for `include::` directives and replace them with the content of the file(s) to include. 
  -If the file to include has an empty last line, it will be ignored, so it's always a good practice to include a blank line after the `include::` directive in the main document, to avoid side-effects during
  -the "full" parsing.
  -Also, the `lines` and `tags` attribute values must use semicolon (`;`) to join multiple ranges when they are not wrapped in quotes, and they can use both colon (`,`) and semicolon within quotes.
  -
  -For example:
  -
  -[source]
  -====
  -pass:[include::chapter-a.adoc[lines=1;3..4;6..10]]
  -
  -pass:[include::chapter-a.adoc[lines="1,3..4,6..10"]]
  -
  -pass:[include::chapter-a.adoc[lines="1;3..4;6..10"]]
  -====
  -
  -== Substitutions
  -
  -In "normal" paragraphs, Asciidoctor processes the content with the following substitutions, in the following order:
  -
  -1. Special characters
  -2. Quotes
  -3. Attribute references
  -4. Replacements
  -5. Inline macros
  -6. Post replacements
  -
  -However, splitting the "Quotes" and "Inline Macros" in two distinct steps causes troubles in LibAsciidoc, when an inline macro is wrapped in quoted text, or when an inline macro contains quoted attributes. 
  -As a consequence, in "normal" paragraphs, LibAsciidoc processes the content with the following substitutions, in the following order:
  -
  -1. Special characters
  -2. Attribute references
  -3. Replacements
  -4. Quotes and Inline macros
  -5. Post replacements
  -
  -
  -
   == Symbols and Characters
   
   Markup for the mdash and arrow symbols is not recognized.
  
positive.code: 
  == Constrained Monospace Text and Quoted Strings or Apostrophes
  
  Constrained or imbalanced monospace text may not act fully constrained, or may be confused in the presence of
  imbalanced quoted strings or apostrophes.  Typically such markup is erroneous, but the results from such errors may
  differ between implementations.
  See https://github.com/bytesparadise/libasciidoc/issues/630[Issue #630].
  
  == Attribute Lists
  
negative.code: 
  This document reports the known limitations and differences with Asciidoc/Asciidoctor.
  In any case, feel free to https://github.com/bytesparadise/libasciidoc/issues[open an issue]
  if you want to discuss an actual limitation of Libasciidoc or if you want to report a new one. We also accept pull requests.
  
  This list is not necessarily complete, but it should reflect the differences
  likely to impact real documents.
  