common subset of #MarkDown, #ReStructedText, and #AsciiDoc

common-plain-markup.txt

MarkDown vs. ReStructuredText vs. Asciidoc
==========================================

.::

    **strong emphasis text**
    ``literal`` (compatible with Asciidoctor)
    > blockquote is compatible with Asciidoctor,
    * unordered list item
    - unordered list item
    1. ordered list item
    ---- for horizontal rule (compatible with Asciidoctor).
    main title for document
    ========================
    (see below)
    title
    -----------------
    Compatibel with Asciidoc python,
    using it  implicitly set `compat-mode` in Asciidoctor,
    (without new Asciidoctor syntax).


Summary
--------

.::

    **storg**
    * unordered list
    - unordered list
    1. ordered list
    main title
    ==========
    title
    ------

Workarounds
-----------

.::

    [Link][1] will display as link in [MarkDown][2],
    and literal in ReStructuredText and AsciiDoc.

    [1]: http://example.com

    [2]: http://example.com


    ReStructuredText requires the precedding paragraph of literal block ends with `::`,
    which is used to mark label list in AsciiDoc.
    However, AsciiDoc allows a string beginning with dot
    to specify filename of source code, which will be parsed literally.
    Combining those we have .::, \n, four-spaces indented literal block.