-.
-
-````````````````````````````````
-
-
-Hard line breaks are for separating inline content within a block.
-Neither syntax for hard line breaks works at the end of a paragraph or
-other block element:
-
-```````````````````````````````` example
-foo\
-.
-foo\
-````````````````````````````````
-
-
-```````````````````````````````` example
-foo
-.
-foo
-````````````````````````````````
-
-
-```````````````````````````````` example
-### foo\
-.
-foo\
-````````````````````````````````
-
-
-```````````````````````````````` example
-### foo
-.
-foo
-````````````````````````````````
-
-
-## Soft line breaks
-
-A regular line break (not in a code span or HTML tag) that is not
-preceded by two or more spaces or a backslash is parsed as a
-[softbreak](@). (A softbreak may be rendered in HTML either as a
-[line ending] or as a space. The result will be the same in
-browsers. In the examples here, a [line ending] will be used.)
-
-```````````````````````````````` example
-foo
-baz
-.
-foo
-baz
-````````````````````````````````
-
-
-Spaces at the end of the line and beginning of the next line are
-removed:
-
-```````````````````````````````` example
-foo
- baz
-.
-foo
-baz
-````````````````````````````````
-
-
-A conforming parser may render a soft line break in HTML either as a
-line break or as a space.
-
-A renderer may also provide an option to render soft line breaks
-as hard line breaks.
-
-## Textual content
-
-Any characters not given an interpretation by the above rules will
-be parsed as plain textual content.
-
-```````````````````````````````` example
-hello $.;'there
-.
-hello $.;'there
-````````````````````````````````
-
-
-```````````````````````````````` example
-Foo χρῆν
-.
-Foo χρῆν
-````````````````````````````````
-
-
-Internal spaces are preserved verbatim:
-
-```````````````````````````````` example
-Multiple spaces
-.
-Multiple spaces
-````````````````````````````````
-
-
-
-
-# Appendix: A parsing strategy
-
-In this appendix we describe some features of the parsing strategy
-used in the CommonMark reference implementations.
-
-## Overview
-
-Parsing has two phases:
-
-1. In the first phase, lines of input are consumed and the block
-structure of the document---its division into paragraphs, block quotes,
-list items, and so on---is constructed. Text is assigned to these
-blocks but not parsed. Link reference definitions are parsed and a
-map of links is constructed.
-
-2. In the second phase, the raw text contents of paragraphs and headings
-are parsed into sequences of Markdown inline elements (strings,
-code spans, links, emphasis, and so on), using the map of link
-references constructed in phase 1.
-
-At each point in processing, the document is represented as a tree of
-**blocks**. The root of the tree is a `document` block. The `document`
-may have any number of other blocks as **children**. These children
-may, in turn, have other blocks as children. The last child of a block
-is normally considered **open**, meaning that subsequent lines of input
-can alter its contents. (Blocks that are not open are **closed**.)
-Here, for example, is a possible document tree, with the open blocks
-marked by arrows:
-
-``` tree
--> document
- -> block_quote
- paragraph
- "Lorem ipsum dolor\nsit amet."
- -> list (type=bullet tight=true bullet_char=-)
- list_item
- paragraph
- "Qui *quodsi iracundia*"
- -> list_item
- -> paragraph
- "aliquando id"
-```
-
-## Phase 1: block structure
-
-Each line that is processed has an effect on this tree. The line is
-analyzed and, depending on its contents, the document may be altered
-in one or more of the following ways:
-
-1. One or more open blocks may be closed.
-2. One or more new blocks may be created as children of the
- last open block.
-3. Text may be added to the last (deepest) open block remaining
- on the tree.
-
-Once a line has been incorporated into the tree in this way,
-it can be discarded, so input can be read in a stream.
-
-For each line, we follow this procedure:
-
-1. First we iterate through the open blocks, starting with the
-root document, and descending through last children down to the last
-open block. Each block imposes a condition that the line must satisfy
-if the block is to remain open. For example, a block quote requires a
-`>` character. A paragraph requires a non-blank line.
-In this phase we may match all or just some of the open
-blocks. But we cannot close unmatched blocks yet, because we may have a
-[lazy continuation line].
-
-2. Next, after consuming the continuation markers for existing
-blocks, we look for new block starts (e.g. `>` for a block quote).
-If we encounter a new block start, we close any blocks unmatched
-in step 1 before creating the new block as a child of the last
-matched block.
-
-3. Finally, we look at the remainder of the line (after block
-markers like `>`, list markers, and indentation have been consumed).
-This is text that can be incorporated into the last open
-block (a paragraph, code block, heading, or raw HTML).
-
-Setext headings are formed when we see a line of a paragraph
-that is a [setext heading underline].
-
-Reference link definitions are detected when a paragraph is closed;
-the accumulated text lines are parsed to see if they begin with
-one or more reference link definitions. Any remainder becomes a
-normal paragraph.
-
-We can see how this works by considering how the tree above is
-generated by four lines of Markdown:
-
-``` markdown
-> Lorem ipsum dolor
-sit amet.
-> - Qui *quodsi iracundia*
-> - aliquando id
-```
-
-At the outset, our document model is just
-
-``` tree
--> document
-```
-
-The first line of our text,
-
-``` markdown
-> Lorem ipsum dolor
-```
-
-causes a `block_quote` block to be created as a child of our
-open `document` block, and a `paragraph` block as a child of
-the `block_quote`. Then the text is added to the last open
-block, the `paragraph`:
-
-``` tree
--> document
- -> block_quote
- -> paragraph
- "Lorem ipsum dolor"
-```
-
-The next line,
-
-``` markdown
-sit amet.
-```
-
-is a "lazy continuation" of the open `paragraph`, so it gets added
-to the paragraph's text:
-
-``` tree
--> document
- -> block_quote
- -> paragraph
- "Lorem ipsum dolor\nsit amet."
-```
-
-The third line,
-
-``` markdown
-> - Qui *quodsi iracundia*
-```
-
-causes the `paragraph` block to be closed, and a new `list` block
-opened as a child of the `block_quote`. A `list_item` is also
-added as a child of the `list`, and a `paragraph` as a child of
-the `list_item`. The text is then added to the new `paragraph`:
-
-``` tree
--> document
- -> block_quote
- paragraph
- "Lorem ipsum dolor\nsit amet."
- -> list (type=bullet tight=true bullet_char=-)
- -> list_item
- -> paragraph
- "Qui *quodsi iracundia*"
-```
-
-The fourth line,
-
-``` markdown
-> - aliquando id
-```
-
-causes the `list_item` (and its child the `paragraph`) to be closed,
-and a new `list_item` opened up as child of the `list`. A `paragraph`
-is added as a child of the new `list_item`, to contain the text.
-We thus obtain the final tree:
-
-``` tree
--> document
- -> block_quote
- paragraph
- "Lorem ipsum dolor\nsit amet."
- -> list (type=bullet tight=true bullet_char=-)
- list_item
- paragraph
- "Qui *quodsi iracundia*"
- -> list_item
- -> paragraph
- "aliquando id"
-```
-
-## Phase 2: inline structure
-
-Once all of the input has been parsed, all open blocks are closed.
-
-We then "walk the tree," visiting every node, and parse raw
-string contents of paragraphs and headings as inlines. At this
-point we have seen all the link reference definitions, so we can
-resolve reference links as we go.
-
-``` tree
-document
- block_quote
- paragraph
- str "Lorem ipsum dolor"
- softbreak
- str "sit amet."
- list (type=bullet tight=true bullet_char=-)
- list_item
- paragraph
- str "Qui "
- emph
- str "quodsi iracundia"
- list_item
- paragraph
- str "aliquando id"
-```
-
-Notice how the [line ending] in the first paragraph has
-been parsed as a `softbreak`, and the asterisks in the first list item
-have become an `emph`.
-
-### An algorithm for parsing nested emphasis and links
-
-By far the trickiest part of inline parsing is handling emphasis,
-strong emphasis, links, and images. This is done using the following
-algorithm.
-
-When we're parsing inlines and we hit either
-
-- a run of `*` or `_` characters, or
-- a `[` or `.
-
-The [delimiter stack] is a doubly linked list. Each
-element contains a pointer to a text node, plus information about
-
-- the type of delimiter (`[`, `![`, `*`, `_`)
-- the number of delimiters,
-- whether the delimiter is "active" (all are active to start), and
-- whether the delimiter is a potential opener, a potential closer,
- or both (which depends on what sort of characters precede
- and follow the delimiters).
-
-When we hit a `]` character, we call the *look for link or image*
-procedure (see below).
-
-When we hit the end of the input, we call the *process emphasis*
-procedure (see below), with `stack_bottom` = NULL.
-
-#### *look for link or image*
-
-Starting at the top of the delimiter stack, we look backwards
-through the stack for an opening `[` or `![` delimiter.
-
-- If we don't find one, we return a literal text node `]`.
-
-- If we do find one, but it's not *active*, we remove the inactive
- delimiter from the stack, and return a literal text node `]`.
-
-- If we find one and it's active, then we parse ahead to see if
- we have an inline link/image, reference link/image, compact reference
- link/image, or shortcut reference link/image.
-
- + If we don't, then we remove the opening delimiter from the
- delimiter stack and return a literal text node `]`.
-
- + If we do, then
-
- * We return a link or image node whose children are the inlines
- after the text node pointed to by the opening delimiter.
-
- * We run *process emphasis* on these inlines, with the `[` opener
- as `stack_bottom`.
-
- * We remove the opening delimiter.
-
- * If we have a link (and not an image), we also set all
- `[` delimiters before the opening delimiter to *inactive*. (This
- will prevent us from getting links within links.)
-
-#### *process emphasis*
-
-Parameter `stack_bottom` sets a lower bound to how far we
-descend in the [delimiter stack]. If it is NULL, we can
-go all the way to the bottom. Otherwise, we stop before
-visiting `stack_bottom`.
-
-Let `current_position` point to the element on the [delimiter stack]
-just above `stack_bottom` (or the first element if `stack_bottom`
-is NULL).
-
-We keep track of the `openers_bottom` for each delimiter
-type (`*`, `_`) and each length of the closing delimiter run
-(modulo 3). Initialize this to `stack_bottom`.
-
-Then we repeat the following until we run out of potential
-closers:
-
-- Move `current_position` forward in the delimiter stack (if needed)
- until we find the first potential closer with delimiter `*` or `_`.
- (This will be the potential closer closest
- to the beginning of the input -- the first one in parse order.)
-
-- Now, look back in the stack (staying above `stack_bottom` and
- the `openers_bottom` for this delimiter type) for the
- first matching potential opener ("matching" means same delimiter).
-
-- If one is found:
-
- + Figure out whether we have emphasis or strong emphasis:
- if both closer and opener spans have length >= 2, we have
- strong, otherwise regular.
-
- + Insert an emph or strong emph node accordingly, after
- the text node corresponding to the opener.
-
- + Remove any delimiters between the opener and closer from
- the delimiter stack.
-
- + Remove 1 (for regular emph) or 2 (for strong emph) delimiters
- from the opening and closing text nodes. If they become empty
- as a result, remove them and remove the corresponding element
- of the delimiter stack. If the closing node is removed, reset
- `current_position` to the next element in the stack.
-
-- If none is found:
-
- + Set `openers_bottom` to the element before `current_position`.
- (We know that there are no openers for this kind of closer up to and
- including this point, so this puts a lower bound on future searches.)
-
- + If the closer at `current_position` is not a potential opener,
- remove it from the delimiter stack (since we know it can't
- be a closer either).
-
- + Advance `current_position` to the next element in the stack.
-
-After we're done, we remove all delimiters above `stack_bottom` from the
-delimiter stack.
-
diff --git a/tests/test_cmark_spec/spec.sh b/tests/test_cmark_spec/spec.sh
deleted file mode 100755
index 034fd86e..00000000
--- a/tests/test_cmark_spec/spec.sh
+++ /dev/null
@@ -1,26 +0,0 @@
-#!/usr/bin/env bash
-
-set -e
-
-REPO="https://github.com/commonmark/CommonMark.git"
-VERSION="0.29"
-
-function main {
- echo "Cloning from repo: $REPO..."
- git clone --quiet $REPO
-
- echo "Using version $VERSION..."
- cd "CommonMark"
- git checkout --quiet $VERSION
-
- echo "Dumping tests file..."
- python3 "test/spec_tests.py" --dump-tests > "../commonmark.json"
-
- echo "Cleaning up..."
- cd ..
- rm -rf CommonMark
-
- echo "Done."
-}
-
-main
diff --git a/tests/test_cmark_spec/test_spec.py b/tests/test_cmark_spec/test_spec.py
deleted file mode 100644
index 18ad4118..00000000
--- a/tests/test_cmark_spec/test_spec.py
+++ /dev/null
@@ -1,38 +0,0 @@
-"""In this module tests are run against the full test set,
-provided by https://github.com/commonmark/CommonMark.git.
-"""
-import json
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-
-SPEC_INPUT = Path(__file__).parent.joinpath("spec.md")
-TESTS_INPUT = Path(__file__).parent.joinpath("commonmark.json")
-
-
-def test_file(file_regression):
- md = MarkdownIt("commonmark")
- file_regression.check(md.render(SPEC_INPUT.read_text()), extension=".html")
-
-
-@pytest.mark.parametrize("entry", json.loads(TESTS_INPUT.read_text()))
-def test_spec(entry):
- if entry["example"] == 599:
- # TODO fix Backslash-escapes do not work inside autolinks
- pytest.skip("autolinks backslash escape")
- md = MarkdownIt("commonmark")
- output = md.render(entry["markdown"])
- expected = entry["html"]
-
- if entry["example"] == 593:
- # this doesn't have any bearing on the output
- output = output.replace("mailto", "MAILTO")
- if entry["example"] in [187, 209, 210]:
- # this doesn't have any bearing on the output
- output = output.replace(
- "", "\n
"
- )
-
- assert output == expected
diff --git a/tests/test_cmark_spec/test_spec/test_file.html b/tests/test_cmark_spec/test_spec/test_file.html
deleted file mode 100644
index af1ede2e..00000000
--- a/tests/test_cmark_spec/test_spec/test_file.html
+++ /dev/null
@@ -1,7136 +0,0 @@
-
-title: CommonMark Spec
-author: John MacFarlane
-version: 0.29
-date: '2019-04-06'
-license: 'CC-BY-SA 4.0'
-...
-Introduction
-What is Markdown?
-Markdown is a plain text format for writing structured documents,
-based on conventions for indicating formatting in email
-and usenet posts. It was developed by John Gruber (with
-help from Aaron Swartz) and released in 2004 in the form of a
-syntax description
-and a Perl script (Markdown.pl) for converting Markdown to
-HTML. In the next decade, dozens of implementations were
-developed in many languages. Some extended the original
-Markdown syntax with conventions for footnotes, tables, and
-other document elements. Some allowed Markdown documents to be
-rendered in formats other than HTML. Websites like Reddit,
-StackOverflow, and GitHub had millions of people using Markdown.
-And Markdown started to be used beyond the web, to author books,
-articles, slide shows, letters, and lecture notes.
-What distinguishes Markdown from many other lightweight markup
-syntaxes, which are often easier to write, is its readability.
-As Gruber writes:
-
-The overriding design goal for Markdown's formatting syntax is
-to make it as readable as possible. The idea is that a
-Markdown-formatted document should be publishable as-is, as
-plain text, without looking like it's been marked up with tags
-or formatting instructions.
-(http://daringfireball.net/projects/markdown/)
-
-The point can be illustrated by comparing a sample of
-AsciiDoc with
-an equivalent sample of Markdown. Here is a sample of
-AsciiDoc from the AsciiDoc manual:
-1. List item one.
-+
-List item one continued with a second paragraph followed by an
-Indented block.
-+
-.................
-$ ls *.sh
-$ mv *.sh ~/tmp
-.................
-+
-List item continued with a third paragraph.
-
-2. List item two continued with an open block.
-+
---
-This paragraph is part of the preceding list item.
-
-a. This list is nested and does not require explicit item
-continuation.
-+
-This paragraph is part of the preceding list item.
-
-b. List item b.
-
-This paragraph belongs to item two of the outer list.
---
-
-And here is the equivalent in Markdown:
-1. List item one.
-
- List item one continued with a second paragraph followed by an
- Indented block.
-
- $ ls *.sh
- $ mv *.sh ~/tmp
-
- List item continued with a third paragraph.
-
-2. List item two continued with an open block.
-
- This paragraph is part of the preceding list item.
-
- 1. This list is nested and does not require explicit item continuation.
-
- This paragraph is part of the preceding list item.
-
- 2. List item b.
-
- This paragraph belongs to item two of the outer list.
-
-The AsciiDoc version is, arguably, easier to write. You don't need
-to worry about indentation. But the Markdown version is much easier
-to read. The nesting of list items is apparent to the eye in the
-source, not just in the processed document.
-Why is a spec needed?
-John Gruber's canonical description of Markdown's
-syntax
-does not specify the syntax unambiguously. Here are some examples of
-questions it does not answer:
-
--
-
How much indentation is needed for a sublist? The spec says that
-continuation paragraphs need to be indented four spaces, but is
-not fully explicit about sublists. It is natural to think that
-they, too, must be indented four spaces, but Markdown.pl does
-not require that. This is hardly a "corner case," and divergences
-between implementations on this issue often lead to surprises for
-users in real documents. (See this comment by John
-Gruber.)
-
--
-
Is a blank line needed before a block quote or heading?
-Most implementations do not require the blank line. However,
-this can lead to unexpected results in hard-wrapped text, and
-also to ambiguities in parsing (note that some implementations
-put the heading inside the blockquote, while others do not).
-(John Gruber has also spoken in favor of requiring the blank
-lines.)
-
--
-
Is a blank line needed before an indented code block?
-(Markdown.pl requires it, but this is not mentioned in the
-documentation, and some implementations do not require it.)
-paragraph
- code?
-
-
--
-
What is the exact rule for determining when list items get
-wrapped in <p> tags? Can a list be partially "loose" and partially
-"tight"? What should we do with a list like this?
-1. one
-
-2. two
-3. three
-
-Or this?
-1. one
- - a
-
- - b
-2. two
-
-(There are some relevant comments by John Gruber
-here.)
-
--
-
Can list markers be indented? Can ordered list markers be right-aligned?
- 8. item 1
- 9. item 2
-10. item 2a
-
-
--
-
Is this one list with a thematic break in its second item,
-or two lists separated by a thematic break?
-* a
-* * * * *
-* b
-
-
--
-
When list markers change from numbers to bullets, do we have
-two lists or one? (The Markdown syntax description suggests two,
-but the perl scripts and many other implementations produce one.)
-1. fee
-2. fie
-- foe
-- fum
-
-
--
-
What are the precedence rules for the markers of inline structure?
-For example, is the following a valid link, or does the code span
-take precedence ?
-[a backtick (`)](/url) and [another backtick (`)](/url).
-
-
--
-
What are the precedence rules for markers of emphasis and strong
-emphasis? For example, how should the following be parsed?
-*foo *bar* baz*
-
-
--
-
What are the precedence rules between block-level and inline-level
-structure? For example, how should the following be parsed?
-- `a long code span can contain a hyphen like this
- - and it can screw things up`
-
-
--
-
Can list items include section headings? (Markdown.pl does not
-allow this, but does allow blockquotes to include headings.)
-- # Heading
-
-
--
-
Can list items be empty?
-* a
-*
-* b
-
-
--
-
Can link references be defined inside block quotes or list items?
-> Blockquote [foo].
->
-> [foo]: /url
-
-
--
-
If there are multiple definitions for the same reference, which takes
-precedence?
-[foo]: /url1
-[foo]: /url2
-
-[foo][]
-
-
-
-In the absence of a spec, early implementers consulted Markdown.pl
-to resolve these ambiguities. But Markdown.pl was quite buggy, and
-gave manifestly bad results in many cases, so it was not a
-satisfactory replacement for a spec.
-Because there is no unambiguous spec, implementations have diverged
-considerably. As a result, users are often surprised to find that
-a document that renders one way on one system (say, a GitHub wiki)
-renders differently on another (say, converting to docbook using
-pandoc). To make matters worse, because nothing in Markdown counts
-as a "syntax error," the divergence often isn't discovered right away.
-About this document
-This document attempts to specify Markdown syntax unambiguously.
-It contains many examples with side-by-side Markdown and
-HTML. These are intended to double as conformance tests. An
-accompanying script spec_tests.py can be used to run the tests
-against any Markdown program:
-python test/spec_tests.py --spec spec.txt --program PROGRAM
-
-Since this document describes how Markdown is to be parsed into
-an abstract syntax tree, it would have made sense to use an abstract
-representation of the syntax tree instead of HTML. But HTML is capable
-of representing the structural distinctions we need to make, and the
-choice of HTML for the tests makes it possible to run the tests against
-an implementation without writing an abstract syntax tree renderer.
-This document is generated from a text file, spec.txt, written
-in Markdown with a small extension for the side-by-side tests.
-The script tools/makespec.py can be used to convert spec.txt into
-HTML or CommonMark (which can then be converted into other formats).
-In the examples, the → character is used to represent tabs.
-Preliminaries
-Characters and lines
-Any sequence of [characters] is a valid CommonMark
-document.
-A character is a Unicode code point. Although some
-code points (for example, combining accents) do not correspond to
-characters in an intuitive sense, all code points count as characters
-for purposes of this spec.
-This spec does not specify an encoding; it thinks of lines as composed
-of [characters] rather than bytes. A conforming parser may be limited
-to a certain encoding.
-A line is a sequence of zero or more [characters]
-other than newline (U+000A) or carriage return (U+000D),
-followed by a [line ending] or by the end of file.
-A line ending is a newline (U+000A), a carriage return
-(U+000D) not followed by a newline, or a carriage return and a
-following newline.
-A line containing no characters, or a line containing only spaces
-(U+0020) or tabs (U+0009), is called a blank line.
-The following definitions of character classes will be used in this spec:
-A whitespace character is a space
-(U+0020), tab (U+0009), newline (U+000A), line tabulation (U+000B),
-form feed (U+000C), or carriage return (U+000D).
-Whitespace is a sequence of one or more [whitespace
-characters].
-A Unicode whitespace character is
-any code point in the Unicode Zs general category, or a tab (U+0009),
-carriage return (U+000D), newline (U+000A), or form feed
-(U+000C).
-Unicode whitespace is a sequence of one
-or more [Unicode whitespace characters].
-A space is U+0020.
-A non-whitespace character is any character
-that is not a [whitespace character].
-An ASCII punctuation character
-is !, ", #, $, %, &, ', (, ),
-*, +, ,, -, ., / (U+0021–2F),
-:, ;, <, =, >, ?, @ (U+003A–0040),
-[, \, ], ^, _, ` (U+005B–0060),
-{, |, }, or ~ (U+007B–007E).
-A punctuation character is an [ASCII
-punctuation character] or anything in
-the general Unicode categories Pc, Pd, Pe, Pf, Pi, Po, or Ps.
-Tabs
-Tabs in lines are not expanded to [spaces]. However,
-in contexts where whitespace helps to define block structure,
-tabs behave as if they were replaced by spaces with a tab stop
-of 4 characters.
-Thus, for example, a tab can be used instead of four spaces
-in an indented code block. (Note, however, that internal
-tabs are passed through as literal tabs, not expanded to
-spaces.)
-→foo→baz→→bim
-.
-<pre><code>foo→baz→→bim
-</code></pre>
-
- →foo→baz→→bim
-.
-<pre><code>foo→baz→→bim
-</code></pre>
-
- a→a
- ὐ→a
-.
-<pre><code>a→a
-ὐ→a
-</code></pre>
-
-In the following example, a continuation paragraph of a list
-item is indented with a tab; this has exactly the same effect
-as indentation with four spaces would:
- - foo
-
-→bar
-.
-<ul>
-<li>
-<p>foo</p>
-<p>bar</p>
-</li>
-</ul>
-
-- foo
-
-→→bar
-.
-<ul>
-<li>
-<p>foo</p>
-<pre><code> bar
-</code></pre>
-</li>
-</ul>
-
-Normally the > that begins a block quote may be followed
-optionally by a space, which is not considered part of the
-content. In the following case > is followed by a tab,
-which is treated as if it were expanded into three spaces.
-Since one of these spaces is considered part of the
-delimiter, foo is considered to be indented six spaces
-inside the block quote context, so we get an indented
-code block starting with two spaces.
->→→foo
-.
-<blockquote>
-<pre><code> foo
-</code></pre>
-</blockquote>
-
--→→foo
-.
-<ul>
-<li>
-<pre><code> foo
-</code></pre>
-</li>
-</ul>
-
- foo
-→bar
-.
-<pre><code>foo
-bar
-</code></pre>
-
- - foo
- - bar
-→ - baz
-.
-<ul>
-<li>foo
-<ul>
-<li>bar
-<ul>
-<li>baz</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-
-#→Foo
-.
-<h1>Foo</h1>
-
-*→*→*→
-.
-<hr />
-
-Insecure characters
-For security reasons, the Unicode character U+0000 must be replaced
-with the REPLACEMENT CHARACTER (U+FFFD).
-Blocks and inlines
-We can think of a document as a sequence of
-blocks---structural elements like paragraphs, block
-quotations, lists, headings, rules, and code blocks. Some blocks (like
-block quotes and list items) contain other blocks; others (like
-headings and paragraphs) contain inline content---text,
-links, emphasized text, images, code spans, and so on.
-Precedence
-Indicators of block structure always take precedence over indicators
-of inline structure. So, for example, the following is a list with
-two items, not a list with one item containing a code span:
-- `one
-- two`
-.
-<ul>
-<li>`one</li>
-<li>two`</li>
-</ul>
-
-This means that parsing can proceed in two steps: first, the block
-structure of the document can be discerned; second, text lines inside
-paragraphs, headings, and other block constructs can be parsed for inline
-structure. The second step requires information about link reference
-definitions that will be available only at the end of the first
-step. Note that the first step requires processing lines in sequence,
-but the second can be parallelized, since the inline parsing of
-one block element does not affect the inline parsing of any other.
-Container blocks and leaf blocks
-We can divide blocks into two types:
-container blocks,
-which can contain other blocks, and leaf blocks,
-which cannot.
-Leaf blocks
-This section describes the different kinds of leaf block that make up a
-Markdown document.
-Thematic breaks
-A line consisting of 0-3 spaces of indentation, followed by a sequence
-of three or more matching -, _, or * characters, each followed
-optionally by any number of spaces or tabs, forms a
-thematic break.
-***
----
-___
-.
-<hr />
-<hr />
-<hr />
-
-Wrong characters:
-+++
-.
-<p>+++</p>
-
-===
-.
-<p>===</p>
-
-Not enough characters:
---
-**
-__
-.
-<p>--
-**
-__</p>
-
-One to three spaces indent are allowed:
- ***
- ***
- ***
-.
-<hr />
-<hr />
-<hr />
-
-Four spaces is too many:
- ***
-.
-<pre><code>***
-</code></pre>
-
-Foo
- ***
-.
-<p>Foo
-***</p>
-
-More than three characters may be used:
-_____________________________________
-.
-<hr />
-
-Spaces are allowed between the characters:
- - - -
-.
-<hr />
-
- ** * ** * ** * **
-.
-<hr />
-
-- - - -
-.
-<hr />
-
-Spaces are allowed at the end:
-- - - -
-.
-<hr />
-
-However, no other characters may occur in the line:
-_ _ _ _ a
-
-a------
-
----a---
-.
-<p>_ _ _ _ a</p>
-<p>a------</p>
-<p>---a---</p>
-
-It is required that all of the [non-whitespace characters] be the same.
-So, this is not a thematic break:
- *-*
-.
-<p><em>-</em></p>
-
-Thematic breaks do not need blank lines before or after:
-- foo
-***
-- bar
-.
-<ul>
-<li>foo</li>
-</ul>
-<hr />
-<ul>
-<li>bar</li>
-</ul>
-
-Thematic breaks can interrupt a paragraph:
-Foo
-***
-bar
-.
-<p>Foo</p>
-<hr />
-<p>bar</p>
-
-If a line of dashes that meets the above conditions for being a
-thematic break could also be interpreted as the underline of a [setext
-heading], the interpretation as a
-[setext heading] takes precedence. Thus, for example,
-this is a setext heading, not a paragraph followed by a thematic break:
-Foo
----
-bar
-.
-<h2>Foo</h2>
-<p>bar</p>
-
-When both a thematic break and a list item are possible
-interpretations of a line, the thematic break takes precedence:
-* Foo
-* * *
-* Bar
-.
-<ul>
-<li>Foo</li>
-</ul>
-<hr />
-<ul>
-<li>Bar</li>
-</ul>
-
-If you want a thematic break in a list item, use a different bullet:
-- Foo
-- * * *
-.
-<ul>
-<li>Foo</li>
-<li>
-<hr />
-</li>
-</ul>
-
-ATX headings
-An ATX heading
-consists of a string of characters, parsed as inline content, between an
-opening sequence of 1--6 unescaped # characters and an optional
-closing sequence of any number of unescaped # characters.
-The opening sequence of # characters must be followed by a
-[space] or by the end of line. The optional closing sequence of #s must be
-preceded by a [space] and may be followed by spaces only. The opening
-# character may be indented 0-3 spaces. The raw contents of the
-heading are stripped of leading and trailing spaces before being parsed
-as inline content. The heading level is equal to the number of #
-characters in the opening sequence.
-Simple headings:
-# foo
-## foo
-### foo
-#### foo
-##### foo
-###### foo
-.
-<h1>foo</h1>
-<h2>foo</h2>
-<h3>foo</h3>
-<h4>foo</h4>
-<h5>foo</h5>
-<h6>foo</h6>
-
-More than six # characters is not a heading:
-####### foo
-.
-<p>####### foo</p>
-
-At least one space is required between the # characters and the
-heading's contents, unless the heading is empty. Note that many
-implementations currently do not require the space. However, the
-space was required by the
-original ATX implementation,
-and it helps prevent things like the following from being parsed as
-headings:
-#5 bolt
-
-#hashtag
-.
-<p>#5 bolt</p>
-<p>#hashtag</p>
-
-This is not a heading, because the first # is escaped:
-\## foo
-.
-<p>## foo</p>
-
-Contents are parsed as inlines:
-# foo *bar* \*baz\*
-.
-<h1>foo <em>bar</em> *baz*</h1>
-
-Leading and trailing [whitespace] is ignored in parsing inline content:
-# foo
-.
-<h1>foo</h1>
-
-One to three spaces indentation are allowed:
- ### foo
- ## foo
- # foo
-.
-<h3>foo</h3>
-<h2>foo</h2>
-<h1>foo</h1>
-
-Four spaces are too much:
- # foo
-.
-<pre><code># foo
-</code></pre>
-
-foo
- # bar
-.
-<p>foo
-# bar</p>
-
-A closing sequence of # characters is optional:
-## foo ##
- ### bar ###
-.
-<h2>foo</h2>
-<h3>bar</h3>
-
-It need not be the same length as the opening sequence:
-# foo ##################################
-##### foo ##
-.
-<h1>foo</h1>
-<h5>foo</h5>
-
-Spaces are allowed after the closing sequence:
-### foo ###
-.
-<h3>foo</h3>
-
-A sequence of # characters with anything but [spaces] following it
-is not a closing sequence, but counts as part of the contents of the
-heading:
-### foo ### b
-.
-<h3>foo ### b</h3>
-
-The closing sequence must be preceded by a space:
-# foo#
-.
-<h1>foo#</h1>
-
-Backslash-escaped # characters do not count as part
-of the closing sequence:
-### foo \###
-## foo #\##
-# foo \#
-.
-<h3>foo ###</h3>
-<h2>foo ###</h2>
-<h1>foo #</h1>
-
-ATX headings need not be separated from surrounding content by blank
-lines, and they can interrupt paragraphs:
-****
-## foo
-****
-.
-<hr />
-<h2>foo</h2>
-<hr />
-
-Foo bar
-# baz
-Bar foo
-.
-<p>Foo bar</p>
-<h1>baz</h1>
-<p>Bar foo</p>
-
-ATX headings can be empty:
-##
-#
-### ###
-.
-<h2></h2>
-<h1></h1>
-<h3></h3>
-
-Setext headings
-A setext heading consists of one or more
-lines of text, each containing at least one [non-whitespace
-character], with no more than 3 spaces indentation, followed by
-a [setext heading underline]. The lines of text must be such
-that, were they not followed by the setext heading underline,
-they would be interpreted as a paragraph: they cannot be
-interpretable as a [code fence], [ATX heading][ATX headings],
-[block quote][block quotes], [thematic break][thematic breaks],
-[list item][list items], or [HTML block][HTML blocks].
-A setext heading underline is a sequence of
-= characters or a sequence of - characters, with no more than 3
-spaces indentation and any number of trailing spaces. If a line
-containing a single - can be interpreted as an
-empty [list items], it should be interpreted this way
-and not as a [setext heading underline].
-The heading is a level 1 heading if = characters are used in
-the [setext heading underline], and a level 2 heading if -
-characters are used. The contents of the heading are the result
-of parsing the preceding lines of text as CommonMark inline
-content.
-In general, a setext heading need not be preceded or followed by a
-blank line. However, it cannot interrupt a paragraph, so when a
-setext heading comes after a paragraph, a blank line is needed between
-them.
-Simple examples:
-Foo *bar*
-=========
-
-Foo *bar*
----------
-.
-<h1>Foo <em>bar</em></h1>
-<h2>Foo <em>bar</em></h2>
-
-The content of the header may span more than one line:
-Foo *bar
-baz*
-====
-.
-<h1>Foo <em>bar
-baz</em></h1>
-
-The contents are the result of parsing the headings's raw
-content as inlines. The heading's raw content is formed by
-concatenating the lines and removing initial and final
-[whitespace].
- Foo *bar
-baz*→
-====
-.
-<h1>Foo <em>bar
-baz</em></h1>
-
-The underlining can be any length:
-Foo
--------------------------
-
-Foo
-=
-.
-<h2>Foo</h2>
-<h1>Foo</h1>
-
-The heading content can be indented up to three spaces, and need
-not line up with the underlining:
- Foo
----
-
- Foo
------
-
- Foo
- ===
-.
-<h2>Foo</h2>
-<h2>Foo</h2>
-<h1>Foo</h1>
-
-Four spaces indent is too much:
- Foo
- ---
-
- Foo
----
-.
-<pre><code>Foo
----
-
-Foo
-</code></pre>
-<hr />
-
-The setext heading underline can be indented up to three spaces, and
-may have trailing spaces:
-Foo
- ----
-.
-<h2>Foo</h2>
-
-Four spaces is too much:
-Foo
- ---
-.
-<p>Foo
----</p>
-
-The setext heading underline cannot contain internal spaces:
-Foo
-= =
-
-Foo
---- -
-.
-<p>Foo
-= =</p>
-<p>Foo</p>
-<hr />
-
-Trailing spaces in the content line do not cause a line break:
-Foo
------
-.
-<h2>Foo</h2>
-
-Nor does a backslash at the end:
-Foo\
-----
-.
-<h2>Foo\</h2>
-
-Since indicators of block structure take precedence over
-indicators of inline structure, the following are setext headings:
-`Foo
-----
-`
-
-<a title="a lot
----
-of dashes"/>
-.
-<h2>`Foo</h2>
-<p>`</p>
-<h2><a title="a lot</h2>
-<p>of dashes"/></p>
-
-The setext heading underline cannot be a [lazy continuation
-line] in a list item or block quote:
-> Foo
----
-.
-<blockquote>
-<p>Foo</p>
-</blockquote>
-<hr />
-
-> foo
-bar
-===
-.
-<blockquote>
-<p>foo
-bar
-===</p>
-</blockquote>
-
-- Foo
----
-.
-<ul>
-<li>Foo</li>
-</ul>
-<hr />
-
-A blank line is needed between a paragraph and a following
-setext heading, since otherwise the paragraph becomes part
-of the heading's content:
-Foo
-Bar
----
-.
-<h2>Foo
-Bar</h2>
-
-But in general a blank line is not required before or after
-setext headings:
----
-Foo
----
-Bar
----
-Baz
-.
-<hr />
-<h2>Foo</h2>
-<h2>Bar</h2>
-<p>Baz</p>
-
-Setext headings cannot be empty:
-
-====
-.
-<p>====</p>
-
-Setext heading text lines must not be interpretable as block
-constructs other than paragraphs. So, the line of dashes
-in these examples gets interpreted as a thematic break:
----
----
-.
-<hr />
-<hr />
-
-- foo
------
-.
-<ul>
-<li>foo</li>
-</ul>
-<hr />
-
- foo
----
-.
-<pre><code>foo
-</code></pre>
-<hr />
-
-> foo
------
-.
-<blockquote>
-<p>foo</p>
-</blockquote>
-<hr />
-
-If you want a heading with > foo as its literal text, you can
-use backslash escapes:
-\> foo
-------
-.
-<h2>> foo</h2>
-
-Compatibility note: Most existing Markdown implementations
-do not allow the text of setext headings to span multiple lines.
-But there is no consensus about how to interpret
-Foo
-bar
----
-baz
-
-One can find four different interpretations:
-
-- paragraph "Foo", heading "bar", paragraph "baz"
-- paragraph "Foo bar", thematic break, paragraph "baz"
-- paragraph "Foo bar --- baz"
-- heading "Foo bar", paragraph "baz"
-
-We find interpretation 4 most natural, and interpretation 4
-increases the expressive power of CommonMark, by allowing
-multiline headings. Authors who want interpretation 1 can
-put a blank line after the first paragraph:
-Foo
-
-bar
----
-baz
-.
-<p>Foo</p>
-<h2>bar</h2>
-<p>baz</p>
-
-Authors who want interpretation 2 can put blank lines around
-the thematic break,
-Foo
-bar
-
----
-
-baz
-.
-<p>Foo
-bar</p>
-<hr />
-<p>baz</p>
-
-or use a thematic break that cannot count as a [setext heading
-underline], such as
-Foo
-bar
-* * *
-baz
-.
-<p>Foo
-bar</p>
-<hr />
-<p>baz</p>
-
-Authors who want interpretation 3 can use backslash escapes:
-Foo
-bar
-\---
-baz
-.
-<p>Foo
-bar
----
-baz</p>
-
-Indented code blocks
-An indented code block is composed of one or more
-[indented chunks] separated by blank lines.
-An indented chunk is a sequence of non-blank lines,
-each indented four or more spaces. The contents of the code block are
-the literal contents of the lines, including trailing
-[line endings], minus four spaces of indentation.
-An indented code block has no [info string].
-An indented code block cannot interrupt a paragraph, so there must be
-a blank line between a paragraph and a following indented code block.
-(A blank line is not needed, however, between a code block and a following
-paragraph.)
- a simple
- indented code block
-.
-<pre><code>a simple
- indented code block
-</code></pre>
-
-If there is any ambiguity between an interpretation of indentation
-as a code block and as indicating that material belongs to a [list
-item][list items], the list item interpretation takes precedence:
- - foo
-
- bar
-.
-<ul>
-<li>
-<p>foo</p>
-<p>bar</p>
-</li>
-</ul>
-
-1. foo
-
- - bar
-.
-<ol>
-<li>
-<p>foo</p>
-<ul>
-<li>bar</li>
-</ul>
-</li>
-</ol>
-
-The contents of a code block are literal text, and do not get parsed
-as Markdown:
- <a/>
- *hi*
-
- - one
-.
-<pre><code><a/>
-*hi*
-
-- one
-</code></pre>
-
-Here we have three chunks separated by blank lines:
- chunk1
-
- chunk2
-
-
-
- chunk3
-.
-<pre><code>chunk1
-
-chunk2
-
-
-
-chunk3
-</code></pre>
-
-Any initial spaces beyond four will be included in the content, even
-in interior blank lines:
- chunk1
-
- chunk2
-.
-<pre><code>chunk1
-
- chunk2
-</code></pre>
-
-An indented code block cannot interrupt a paragraph. (This
-allows hanging indents and the like.)
-Foo
- bar
-
-.
-<p>Foo
-bar</p>
-
-However, any non-blank line with fewer than four leading spaces ends
-the code block immediately. So a paragraph may occur immediately
-after indented code:
- foo
-bar
-.
-<pre><code>foo
-</code></pre>
-<p>bar</p>
-
-And indented code can occur immediately before and after other kinds of
-blocks:
-# Heading
- foo
-Heading
-------
- foo
-----
-.
-<h1>Heading</h1>
-<pre><code>foo
-</code></pre>
-<h2>Heading</h2>
-<pre><code>foo
-</code></pre>
-<hr />
-
-The first line can be indented more than four spaces:
- foo
- bar
-.
-<pre><code> foo
-bar
-</code></pre>
-
-Blank lines preceding or following an indented code block
-are not included in it:
-
-
- foo
-
-
-.
-<pre><code>foo
-</code></pre>
-
-Trailing spaces are included in the code block's content:
- foo
-.
-<pre><code>foo
-</code></pre>
-
-Fenced code blocks
-A code fence is a sequence
-of at least three consecutive backtick characters (`) or
-tildes (~). (Tildes and backticks cannot be mixed.)
-A fenced code block
-begins with a code fence, indented no more than three spaces.
-The line with the opening code fence may optionally contain some text
-following the code fence; this is trimmed of leading and trailing
-whitespace and called the info string. If the [info string] comes
-after a backtick fence, it may not contain any backtick
-characters. (The reason for this restriction is that otherwise
-some inline code would be incorrectly interpreted as the
-beginning of a fenced code block.)
-The content of the code block consists of all subsequent lines, until
-a closing [code fence] of the same type as the code block
-began with (backticks or tildes), and with at least as many backticks
-or tildes as the opening code fence. If the leading code fence is
-indented N spaces, then up to N spaces of indentation are removed from
-each line of the content (if present). (If a content line is not
-indented, it is preserved unchanged. If it is indented less than N
-spaces, all of the indentation is removed.)
-The closing code fence may be indented up to three spaces, and may be
-followed only by spaces, which are ignored. If the end of the
-containing block (or document) is reached and no closing code fence
-has been found, the code block contains all of the lines after the
-opening code fence until the end of the containing block (or
-document). (An alternative spec would require backtracking in the
-event that a closing code fence is not found. But this makes parsing
-much less efficient, and there seems to be no real down side to the
-behavior described here.)
-A fenced code block may interrupt a paragraph, and does not require
-a blank line either before or after.
-The content of a code fence is treated as literal text, not parsed
-as inlines. The first word of the [info string] is typically used to
-specify the language of the code sample, and rendered in the class
-attribute of the code tag. However, this spec does not mandate any
-particular treatment of the [info string].
-Here is a simple example with backticks:
-```
-<
- >
-```
-.
-<pre><code><
- >
-</code></pre>
-
-With tildes:
-~~~
-<
- >
-~~~
-.
-<pre><code><
- >
-</code></pre>
-
-Fewer than three backticks is not enough:
-``
-foo
-``
-.
-<p><code>foo</code></p>
-
-The closing code fence must use the same character as the opening
-fence:
-```
-aaa
-~~~
-```
-.
-<pre><code>aaa
-~~~
-</code></pre>
-
-~~~
-aaa
-```
-~~~
-.
-<pre><code>aaa
-```
-</code></pre>
-
-The closing code fence must be at least as long as the opening fence:
-````
-aaa
-```
-``````
-.
-<pre><code>aaa
-```
-</code></pre>
-
-~~~~
-aaa
-~~~
-~~~~
-.
-<pre><code>aaa
-~~~
-</code></pre>
-
-Unclosed code blocks are closed by the end of the document
-(or the enclosing [block quote][block quotes] or [list item][list items]):
-```
-.
-<pre><code></code></pre>
-
-`````
-
-```
-aaa
-.
-<pre><code>
-```
-aaa
-</code></pre>
-
-> ```
-> aaa
-
-bbb
-.
-<blockquote>
-<pre><code>aaa
-</code></pre>
-</blockquote>
-<p>bbb</p>
-
-A code block can have all empty lines as its content:
-```
-
-
-```
-.
-<pre><code>
-
-</code></pre>
-
-A code block can be empty:
-```
-```
-.
-<pre><code></code></pre>
-
-Fences can be indented. If the opening fence is indented,
-content lines will have equivalent opening indentation removed,
-if present:
- ```
- aaa
-aaa
-```
-.
-<pre><code>aaa
-aaa
-</code></pre>
-
- ```
-aaa
- aaa
-aaa
- ```
-.
-<pre><code>aaa
-aaa
-aaa
-</code></pre>
-
- ```
- aaa
- aaa
- aaa
- ```
-.
-<pre><code>aaa
- aaa
-aaa
-</code></pre>
-
-Four spaces indentation produces an indented code block:
- ```
- aaa
- ```
-.
-<pre><code>```
-aaa
-```
-</code></pre>
-
-Closing fences may be indented by 0-3 spaces, and their indentation
-need not match that of the opening fence:
-```
-aaa
- ```
-.
-<pre><code>aaa
-</code></pre>
-
- ```
-aaa
- ```
-.
-<pre><code>aaa
-</code></pre>
-
-This is not a closing fence, because it is indented 4 spaces:
-```
-aaa
- ```
-.
-<pre><code>aaa
- ```
-</code></pre>
-
-Code fences (opening and closing) cannot contain internal spaces:
-``` ```
-aaa
-.
-<p><code> </code>
-aaa</p>
-
-~~~~~~
-aaa
-~~~ ~~
-.
-<pre><code>aaa
-~~~ ~~
-</code></pre>
-
-Fenced code blocks can interrupt paragraphs, and can be followed
-directly by paragraphs, without a blank line between:
-foo
-```
-bar
-```
-baz
-.
-<p>foo</p>
-<pre><code>bar
-</code></pre>
-<p>baz</p>
-
-Other blocks can also occur before and after fenced code blocks
-without an intervening blank line:
-foo
----
-~~~
-bar
-~~~
-# baz
-.
-<h2>foo</h2>
-<pre><code>bar
-</code></pre>
-<h1>baz</h1>
-
-An [info string] can be provided after the opening code fence.
-Although this spec doesn't mandate any particular treatment of
-the info string, the first word is typically used to specify
-the language of the code block. In HTML output, the language is
-normally indicated by adding a class to the code element consisting
-of language- followed by the language name.
-```ruby
-def foo(x)
- return 3
-end
-```
-.
-<pre><code class="language-ruby">def foo(x)
- return 3
-end
-</code></pre>
-
-~~~~ ruby startline=3 $%@#$
-def foo(x)
- return 3
-end
-~~~~~~~
-.
-<pre><code class="language-ruby">def foo(x)
- return 3
-end
-</code></pre>
-
-````;
-````
-.
-<pre><code class="language-;"></code></pre>
-
-[Info strings] for backtick code blocks cannot contain backticks:
-``` aa ```
-foo
-.
-<p><code>aa</code>
-foo</p>
-
-[Info strings] for tilde code blocks can contain backticks and tildes:
-~~~ aa ``` ~~~
-foo
-~~~
-.
-<pre><code class="language-aa">foo
-</code></pre>
-
-Closing code fences cannot have [info strings]:
-```
-``` aaa
-```
-.
-<pre><code>``` aaa
-</code></pre>
-
-HTML blocks
-An HTML block is a group of lines that is treated
-as raw HTML (and will not be escaped in HTML output).
-There are seven kinds of [HTML block], which can be defined by their
-start and end conditions. The block begins with a line that meets a
-start condition (after up to three spaces optional indentation).
-It ends with the first subsequent line that meets a matching end
-condition, or the last line of the document, or the last line of
-the container block containing the current HTML
-block, if no line is encountered that meets the [end condition]. If
-the first line meets both the [start condition] and the [end
-condition], the block will contain just that line.
-
--
-
Start condition: line begins with the string <script,
-<pre, or <style (case-insensitive), followed by whitespace,
-the string >, or the end of the line.
-End condition: line contains an end tag
-</script>, </pre>, or </style> (case-insensitive; it
-need not match the start tag).
-
--
-
Start condition: line begins with the string <!--.
-End condition: line contains the string -->.
-
--
-
Start condition: line begins with the string <?.
-End condition: line contains the string ?>.
-
--
-
Start condition: line begins with the string <!
-followed by an uppercase ASCII letter.
-End condition: line contains the character >.
-
--
-
Start condition: line begins with the string
-<![CDATA[.
-End condition: line contains the string ]]>.
-
--
-
Start condition: line begins the string < or </
-followed by one of the strings (case-insensitive) address,
-article, aside, base, basefont, blockquote, body,
-caption, center, col, colgroup, dd, details, dialog,
-dir, div, dl, dt, fieldset, figcaption, figure,
-footer, form, frame, frameset,
-h1, h2, h3, h4, h5, h6, head, header, hr,
-html, iframe, legend, li, link, main, menu, menuitem,
-nav, noframes, ol, optgroup, option, p, param,
-section, source, summary, table, tbody, td,
-tfoot, th, thead, title, tr, track, ul, followed
-by [whitespace], the end of the line, the string >, or
-the string />.
-End condition: line is followed by a [blank line].
-
--
-
Start condition: line begins with a complete [open tag]
-(with any [tag name] other than script,
-style, or pre) or a complete [closing tag],
-followed only by [whitespace] or the end of the line.
-End condition: line is followed by a [blank line].
-
-
-HTML blocks continue until they are closed by their appropriate
-[end condition], or the last line of the document or other container
-block. This means any HTML within an HTML
-block that might otherwise be recognised as a start condition will
-be ignored by the parser and passed through as-is, without changing
-the parser's state.
-For instance, <pre> within a HTML block started by <table> will not affect
-the parser state; as the HTML block was started in by start condition 6, it
-will end at any blank line. This can be surprising:
-<table><tr><td>
-<pre>
-**Hello**,
-
-_world_.
-</pre>
-</td></tr></table>
-.
-<table><tr><td>
-<pre>
-**Hello**,
-<p><em>world</em>.
-</pre></p>
-</td></tr></table>
-
-In this case, the HTML block is terminated by the newline — the **Hello**
-text remains verbatim — and regular parsing resumes, with a paragraph,
-emphasised world and inline and block HTML following.
-All types of [HTML blocks] except type 7 may interrupt
-a paragraph. Blocks of type 7 may not interrupt a paragraph.
-(This restriction is intended to prevent unwanted interpretation
-of long tags inside a wrapped paragraph as starting HTML blocks.)
-Some simple examples follow. Here are some basic HTML blocks
-of type 6:
-<table>
- <tr>
- <td>
- hi
- </td>
- </tr>
-</table>
-
-okay.
-.
-<table>
- <tr>
- <td>
- hi
- </td>
- </tr>
-</table>
-<p>okay.</p>
-
- <div>
- *hello*
- <foo><a>
-.
- <div>
- *hello*
- <foo><a>
-
-A block can also start with a closing tag:
-</div>
-*foo*
-.
-</div>
-*foo*
-
-Here we have two HTML blocks with a Markdown paragraph between them:
-<DIV CLASS="foo">
-
-*Markdown*
-
-</DIV>
-.
-<DIV CLASS="foo">
-<p><em>Markdown</em></p>
-</DIV>
-
-The tag on the first line can be partial, as long
-as it is split where there would be whitespace:
-<div id="foo"
- class="bar">
-</div>
-.
-<div id="foo"
- class="bar">
-</div>
-
-<div id="foo" class="bar
- baz">
-</div>
-.
-<div id="foo" class="bar
- baz">
-</div>
-
-An open tag need not be closed:
-<div>
-*foo*
-
-*bar*
-.
-<div>
-*foo*
-<p><em>bar</em></p>
-
-A partial tag need not even be completed (garbage
-in, garbage out):
-<div id="foo"
-*hi*
-.
-<div id="foo"
-*hi*
-
-<div class
-foo
-.
-<div class
-foo
-
-The initial tag doesn't even need to be a valid
-tag, as long as it starts like one:
-<div *???-&&&-<---
-*foo*
-.
-<div *???-&&&-<---
-*foo*
-
-In type 6 blocks, the initial tag need not be on a line by
-itself:
-<div><a href="bar">*foo*</a></div>
-.
-<div><a href="bar">*foo*</a></div>
-
-<table><tr><td>
-foo
-</td></tr></table>
-.
-<table><tr><td>
-foo
-</td></tr></table>
-
-Everything until the next blank line or end of document
-gets included in the HTML block. So, in the following
-example, what looks like a Markdown code block
-is actually part of the HTML block, which continues until a blank
-line or the end of the document is reached:
-<div></div>
-``` c
-int x = 33;
-```
-.
-<div></div>
-``` c
-int x = 33;
-```
-
-To start an [HTML block] with a tag that is not in the
-list of block-level tags in (6), you must put the tag by
-itself on the first line (and it must be complete):
-<a href="foo">
-*bar*
-</a>
-.
-<a href="foo">
-*bar*
-</a>
-
-In type 7 blocks, the [tag name] can be anything:
-<Warning>
-*bar*
-</Warning>
-.
-<Warning>
-*bar*
-</Warning>
-
-<i class="foo">
-*bar*
-</i>
-.
-<i class="foo">
-*bar*
-</i>
-
-</ins>
-*bar*
-.
-</ins>
-*bar*
-
-These rules are designed to allow us to work with tags that
-can function as either block-level or inline-level tags.
-The <del> tag is a nice example. We can surround content with
-<del> tags in three different ways. In this case, we get a raw
-HTML block, because the <del> tag is on a line by itself:
-<del>
-*foo*
-</del>
-.
-<del>
-*foo*
-</del>
-
-In this case, we get a raw HTML block that just includes
-the <del> tag (because it ends with the following blank
-line). So the contents get interpreted as CommonMark:
-<del>
-
-*foo*
-
-</del>
-.
-<del>
-<p><em>foo</em></p>
-</del>
-
-Finally, in this case, the <del> tags are interpreted
-as [raw HTML] inside the CommonMark paragraph. (Because
-the tag is not on a line by itself, we get inline HTML
-rather than an [HTML block].)
-<del>*foo*</del>
-.
-<p><del><em>foo</em></del></p>
-
-HTML tags designed to contain literal content
-(script, style, pre), comments, processing instructions,
-and declarations are treated somewhat differently.
-Instead of ending at the first blank line, these blocks
-end at the first line containing a corresponding end tag.
-As a result, these blocks can contain blank lines:
-A pre tag (type 1):
-<pre language="haskell"><code>
-import Text.HTML.TagSoup
-
-main :: IO ()
-main = print $ parseTags tags
-</code></pre>
-okay
-.
-<pre language="haskell"><code>
-import Text.HTML.TagSoup
-
-main :: IO ()
-main = print $ parseTags tags
-</code></pre>
-<p>okay</p>
-
-A script tag (type 1):
-<script type="text/javascript">
-// JavaScript example
-
-document.getElementById("demo").innerHTML = "Hello JavaScript!";
-</script>
-okay
-.
-<script type="text/javascript">
-// JavaScript example
-
-document.getElementById("demo").innerHTML = "Hello JavaScript!";
-</script>
-<p>okay</p>
-
-A style tag (type 1):
-<style
- type="text/css">
-h1 {color:red;}
-
-p {color:blue;}
-</style>
-okay
-.
-<style
- type="text/css">
-h1 {color:red;}
-
-p {color:blue;}
-</style>
-<p>okay</p>
-
-If there is no matching end tag, the block will end at the
-end of the document (or the enclosing [block quote][block quotes]
-or [list item][list items]):
-<style
- type="text/css">
-
-foo
-.
-<style
- type="text/css">
-
-foo
-
-> <div>
-> foo
-
-bar
-.
-<blockquote>
-<div>
-foo
-</blockquote>
-<p>bar</p>
-
-- <div>
-- foo
-.
-<ul>
-<li>
-<div>
-</li>
-<li>foo</li>
-</ul>
-
-The end tag can occur on the same line as the start tag:
-<style>p{color:red;}</style>
-*foo*
-.
-<style>p{color:red;}</style>
-<p><em>foo</em></p>
-
-<!-- foo -->*bar*
-*baz*
-.
-<!-- foo -->*bar*
-<p><em>baz</em></p>
-
-Note that anything on the last line after the
-end tag will be included in the [HTML block]:
-<script>
-foo
-</script>1. *bar*
-.
-<script>
-foo
-</script>1. *bar*
-
-A comment (type 2):
-<!-- Foo
-
-bar
- baz -->
-okay
-.
-<!-- Foo
-
-bar
- baz -->
-<p>okay</p>
-
-A processing instruction (type 3):
-<?php
-
- echo '>';
-
-?>
-okay
-.
-<?php
-
- echo '>';
-
-?>
-<p>okay</p>
-
-A declaration (type 4):
-<!DOCTYPE html>
-.
-<!DOCTYPE html>
-
-CDATA (type 5):
-<![CDATA[
-function matchwo(a,b)
-{
- if (a < b && a < 0) then {
- return 1;
-
- } else {
-
- return 0;
- }
-}
-]]>
-okay
-.
-<![CDATA[
-function matchwo(a,b)
-{
- if (a < b && a < 0) then {
- return 1;
-
- } else {
-
- return 0;
- }
-}
-]]>
-<p>okay</p>
-
-The opening tag can be indented 1-3 spaces, but not 4:
- <!-- foo -->
-
- <!-- foo -->
-.
- <!-- foo -->
-<pre><code><!-- foo -->
-</code></pre>
-
- <div>
-
- <div>
-.
- <div>
-<pre><code><div>
-</code></pre>
-
-An HTML block of types 1--6 can interrupt a paragraph, and need not be
-preceded by a blank line.
-Foo
-<div>
-bar
-</div>
-.
-<p>Foo</p>
-<div>
-bar
-</div>
-
-However, a following blank line is needed, except at the end of
-a document, and except for blocks of types 1--5, [above][HTML
-block]:
-<div>
-bar
-</div>
-*foo*
-.
-<div>
-bar
-</div>
-*foo*
-
-HTML blocks of type 7 cannot interrupt a paragraph:
-Foo
-<a href="bar">
-baz
-.
-<p>Foo
-<a href="bar">
-baz</p>
-
-This rule differs from John Gruber's original Markdown syntax
-specification, which says:
-
-The only restrictions are that block-level HTML elements —
-e.g. <div>, <table>, <pre>, <p>, etc. — must be separated from
-surrounding content by blank lines, and the start and end tags of the
-block should not be indented with tabs or spaces.
-
-In some ways Gruber's rule is more restrictive than the one given
-here:
-
-- It requires that an HTML block be preceded by a blank line.
-- It does not allow the start tag to be indented.
-- It requires a matching end tag, which it also does not allow to
-be indented.
-
-Most Markdown implementations (including some of Gruber's own) do not
-respect all of these restrictions.
-There is one respect, however, in which Gruber's rule is more liberal
-than the one given here, since it allows blank lines to occur inside
-an HTML block. There are two reasons for disallowing them here.
-First, it removes the need to parse balanced tags, which is
-expensive and can require backtracking from the end of the document
-if no matching end tag is found. Second, it provides a very simple
-and flexible way of including Markdown content inside HTML tags:
-simply separate the Markdown from the HTML using blank lines:
-Compare:
-<div>
-
-*Emphasized* text.
-
-</div>
-.
-<div>
-<p><em>Emphasized</em> text.</p>
-</div>
-
-<div>
-*Emphasized* text.
-</div>
-.
-<div>
-*Emphasized* text.
-</div>
-
-Some Markdown implementations have adopted a convention of
-interpreting content inside tags as text if the open tag has
-the attribute markdown=1. The rule given above seems a simpler and
-more elegant way of achieving the same expressive power, which is also
-much simpler to parse.
-The main potential drawback is that one can no longer paste HTML
-blocks into Markdown documents with 100% reliability. However,
-in most cases this will work fine, because the blank lines in
-HTML are usually followed by HTML block tags. For example:
-<table>
-
-<tr>
-
-<td>
-Hi
-</td>
-
-</tr>
-
-</table>
-.
-<table>
-<tr>
-<td>
-Hi
-</td>
-</tr>
-</table>
-
-There are problems, however, if the inner tags are indented
-and separated by spaces, as then they will be interpreted as
-an indented code block:
-<table>
-
- <tr>
-
- <td>
- Hi
- </td>
-
- </tr>
-
-</table>
-.
-<table>
- <tr>
-<pre><code><td>
- Hi
-</td>
-</code></pre>
- </tr>
-</table>
-
-Fortunately, blank lines are usually not necessary and can be
-deleted. The exception is inside <pre> tags, but as described
-[above][HTML blocks], raw HTML blocks starting with <pre>
-can contain blank lines.
-Link reference definitions
-A link reference definition
-consists of a [link label], indented up to three spaces, followed
-by a colon (:), optional [whitespace] (including up to one
-[line ending]), a [link destination],
-optional [whitespace] (including up to one
-[line ending]), and an optional [link
-title], which if it is present must be separated
-from the [link destination] by [whitespace].
-No further [non-whitespace characters] may occur on the line.
-A [link reference definition]
-does not correspond to a structural element of a document. Instead, it
-defines a label which can be used in [reference links]
-and reference-style [images] elsewhere in the document. [Link
-reference definitions] can come either before or after the links that use
-them.
-[foo]: /url "title"
-
-[foo]
-.
-<p><a href="/url" title="title">foo</a></p>
-
- [foo]:
- /url
- 'the title'
-
-[foo]
-.
-<p><a href="/url" title="the title">foo</a></p>
-
-[Foo*bar\]]:my_(url) 'title (with parens)'
-
-[Foo*bar\]]
-.
-<p><a href="my_(url)" title="title (with parens)">Foo*bar]</a></p>
-
-[Foo bar]:
-<my url>
-'title'
-
-[Foo bar]
-.
-<p><a href="my%20url" title="title">Foo bar</a></p>
-
-The title may extend over multiple lines:
-[foo]: /url '
-title
-line1
-line2
-'
-
-[foo]
-.
-<p><a href="/url" title="
-title
-line1
-line2
-">foo</a></p>
-
-However, it may not contain a [blank line]:
-[foo]: /url 'title
-
-with blank line'
-
-[foo]
-.
-<p>[foo]: /url 'title</p>
-<p>with blank line'</p>
-<p>[foo]</p>
-
-The title may be omitted:
-[foo]:
-/url
-
-[foo]
-.
-<p><a href="/url">foo</a></p>
-
-The link destination may not be omitted:
-[foo]:
-
-[foo]
-.
-<p>[foo]:</p>
-<p>[foo]</p>
-
-However, an empty link destination may be specified using
-angle brackets:
-[foo]: <>
-
-[foo]
-.
-<p><a href="">foo</a></p>
-
-The title must be separated from the link destination by
-whitespace:
-[foo]: <bar>(baz)
-
-[foo]
-.
-<p>[foo]: <bar>(baz)</p>
-<p>[foo]</p>
-
-Both title and destination can contain backslash escapes
-and literal backslashes:
-[foo]: /url\bar\*baz "foo\"bar\baz"
-
-[foo]
-.
-<p><a href="/url%5Cbar*baz" title="foo"bar\baz">foo</a></p>
-
-A link can come before its corresponding definition:
-[foo]
-
-[foo]: url
-.
-<p><a href="url">foo</a></p>
-
-If there are several matching definitions, the first one takes
-precedence:
-[foo]
-
-[foo]: first
-[foo]: second
-.
-<p><a href="first">foo</a></p>
-
-As noted in the section on [Links], matching of labels is
-case-insensitive (see [matches]).
-[FOO]: /url
-
-[Foo]
-.
-<p><a href="/url">Foo</a></p>
-
-[ΑΓΩ]: /φου
-
-[αγω]
-.
-<p><a href="/%CF%86%CE%BF%CF%85">αγω</a></p>
-
-Here is a link reference definition with no corresponding link.
-It contributes nothing to the document.
-[foo]: /url
-.
-
-Here is another one:
-[
-foo
-]: /url
-bar
-.
-<p>bar</p>
-
-This is not a link reference definition, because there are
-[non-whitespace characters] after the title:
-[foo]: /url "title" ok
-.
-<p>[foo]: /url "title" ok</p>
-
-This is a link reference definition, but it has no title:
-[foo]: /url
-"title" ok
-.
-<p>"title" ok</p>
-
-This is not a link reference definition, because it is indented
-four spaces:
- [foo]: /url "title"
-
-[foo]
-.
-<pre><code>[foo]: /url "title"
-</code></pre>
-<p>[foo]</p>
-
-This is not a link reference definition, because it occurs inside
-a code block:
-```
-[foo]: /url
-```
-
-[foo]
-.
-<pre><code>[foo]: /url
-</code></pre>
-<p>[foo]</p>
-
-A [link reference definition] cannot interrupt a paragraph.
-Foo
-[bar]: /baz
-
-[bar]
-.
-<p>Foo
-[bar]: /baz</p>
-<p>[bar]</p>
-
-However, it can directly follow other block elements, such as headings
-and thematic breaks, and it need not be followed by a blank line.
-# [Foo]
-[foo]: /url
-> bar
-.
-<h1><a href="/url">Foo</a></h1>
-<blockquote>
-<p>bar</p>
-</blockquote>
-
-[foo]: /url
-bar
-===
-[foo]
-.
-<h1>bar</h1>
-<p><a href="/url">foo</a></p>
-
-[foo]: /url
-===
-[foo]
-.
-<p>===
-<a href="/url">foo</a></p>
-
-Several [link reference definitions]
-can occur one after another, without intervening blank lines.
-[foo]: /foo-url "foo"
-[bar]: /bar-url
- "bar"
-[baz]: /baz-url
-
-[foo],
-[bar],
-[baz]
-.
-<p><a href="/foo-url" title="foo">foo</a>,
-<a href="/bar-url" title="bar">bar</a>,
-<a href="/baz-url">baz</a></p>
-
-[Link reference definitions] can occur
-inside block containers, like lists and block quotations. They
-affect the entire document, not just the container in which they
-are defined:
-[foo]
-
-> [foo]: /url
-.
-<p><a href="/url">foo</a></p>
-<blockquote>
-</blockquote>
-
-Whether something is a [link reference definition] is
-independent of whether the link reference it defines is
-used in the document. Thus, for example, the following
-document contains just a link reference definition, and
-no visible content:
-[foo]: /url
-.
-
-Paragraphs
-A sequence of non-blank lines that cannot be interpreted as other
-kinds of blocks forms a paragraph.
-The contents of the paragraph are the result of parsing the
-paragraph's raw content as inlines. The paragraph's raw content
-is formed by concatenating the lines and removing initial and final
-[whitespace].
-A simple example with two paragraphs:
-aaa
-
-bbb
-.
-<p>aaa</p>
-<p>bbb</p>
-
-Paragraphs can contain multiple lines, but no blank lines:
-aaa
-bbb
-
-ccc
-ddd
-.
-<p>aaa
-bbb</p>
-<p>ccc
-ddd</p>
-
-Multiple blank lines between paragraph have no effect:
-aaa
-
-
-bbb
-.
-<p>aaa</p>
-<p>bbb</p>
-
-Leading spaces are skipped:
- aaa
- bbb
-.
-<p>aaa
-bbb</p>
-
-Lines after the first may be indented any amount, since indented
-code blocks cannot interrupt paragraphs.
-aaa
- bbb
- ccc
-.
-<p>aaa
-bbb
-ccc</p>
-
-However, the first line may be indented at most three spaces,
-or an indented code block will be triggered:
- aaa
-bbb
-.
-<p>aaa
-bbb</p>
-
- aaa
-bbb
-.
-<pre><code>aaa
-</code></pre>
-<p>bbb</p>
-
-Final spaces are stripped before inline parsing, so a paragraph
-that ends with two or more spaces will not end with a [hard line
-break]:
-aaa
-bbb
-.
-<p>aaa<br />
-bbb</p>
-
-Blank lines
-[Blank lines] between block-level elements are ignored,
-except for the role they play in determining whether a [list]
-is [tight] or [loose].
-Blank lines at the beginning and end of the document are also ignored.
-
-
-aaa
-
-
-# aaa
-
-
-.
-<p>aaa</p>
-<h1>aaa</h1>
-
-Container blocks
-A container block is a block that has other
-blocks as its contents. There are two basic kinds of container blocks:
-[block quotes] and [list items].
-[Lists] are meta-containers for [list items].
-We define the syntax for container blocks recursively. The general
-form of the definition is:
-
-If X is a sequence of blocks, then the result of
-transforming X in such-and-such a way is a container of type Y
-with these blocks as its content.
-
-So, we explain what counts as a block quote or list item by explaining
-how these can be generated from their contents. This should suffice
-to define the syntax, although it does not give a recipe for parsing
-these constructions. (A recipe is provided below in the section entitled
-A parsing strategy.)
-Block quotes
-A block quote marker
-consists of 0-3 spaces of initial indent, plus (a) the character > together
-with a following space, or (b) a single character > not followed by a space.
-The following rules define [block quotes]:
-
--
-
Basic case. If a string of lines Ls constitute a sequence
-of blocks Bs, then the result of prepending a [block quote
-marker] to the beginning of each line in Ls
-is a block quote containing Bs.
-
--
-
Laziness. If a string of lines Ls constitute a block
-quote with contents Bs, then the result of deleting
-the initial [block quote marker] from one or
-more lines in which the next [non-whitespace character] after the [block
-quote marker] is [paragraph continuation
-text] is a block quote with Bs as its content.
-Paragraph continuation text is text
-that will be parsed as part of the content of a paragraph, but does
-not occur at the beginning of the paragraph.
-
--
-
Consecutiveness. A document cannot contain two [block
-quotes] in a row unless there is a [blank line] between them.
-
-
-Nothing else counts as a block quote.
-Here is a simple example:
-> # Foo
-> bar
-> baz
-.
-<blockquote>
-<h1>Foo</h1>
-<p>bar
-baz</p>
-</blockquote>
-
-The spaces after the > characters can be omitted:
-># Foo
->bar
-> baz
-.
-<blockquote>
-<h1>Foo</h1>
-<p>bar
-baz</p>
-</blockquote>
-
-The > characters can be indented 1-3 spaces:
- > # Foo
- > bar
- > baz
-.
-<blockquote>
-<h1>Foo</h1>
-<p>bar
-baz</p>
-</blockquote>
-
-Four spaces gives us a code block:
- > # Foo
- > bar
- > baz
-.
-<pre><code>> # Foo
-> bar
-> baz
-</code></pre>
-
-The Laziness clause allows us to omit the > before
-[paragraph continuation text]:
-> # Foo
-> bar
-baz
-.
-<blockquote>
-<h1>Foo</h1>
-<p>bar
-baz</p>
-</blockquote>
-
-A block quote can contain some lazy and some non-lazy
-continuation lines:
-> bar
-baz
-> foo
-.
-<blockquote>
-<p>bar
-baz
-foo</p>
-</blockquote>
-
-Laziness only applies to lines that would have been continuations of
-paragraphs had they been prepended with [block quote markers].
-For example, the > cannot be omitted in the second line of
-> foo
-> ---
-
-without changing the meaning:
-> foo
----
-.
-<blockquote>
-<p>foo</p>
-</blockquote>
-<hr />
-
-Similarly, if we omit the > in the second line of
-> - foo
-> - bar
-
-then the block quote ends after the first line:
-> - foo
-- bar
-.
-<blockquote>
-<ul>
-<li>foo</li>
-</ul>
-</blockquote>
-<ul>
-<li>bar</li>
-</ul>
-
-For the same reason, we can't omit the > in front of
-subsequent lines of an indented or fenced code block:
-> foo
- bar
-.
-<blockquote>
-<pre><code>foo
-</code></pre>
-</blockquote>
-<pre><code>bar
-</code></pre>
-
-> ```
-foo
-```
-.
-<blockquote>
-<pre><code></code></pre>
-</blockquote>
-<p>foo</p>
-<pre><code></code></pre>
-
-Note that in the following case, we have a [lazy
-continuation line]:
-> foo
- - bar
-.
-<blockquote>
-<p>foo
-- bar</p>
-</blockquote>
-
-To see why, note that in
-> foo
-> - bar
-
-the - bar is indented too far to start a list, and can't
-be an indented code block because indented code blocks cannot
-interrupt paragraphs, so it is [paragraph continuation text].
-A block quote can be empty:
->
-.
-<blockquote>
-</blockquote>
-
->
->
->
-.
-<blockquote>
-</blockquote>
-
-A block quote can have initial or final blank lines:
->
-> foo
->
-.
-<blockquote>
-<p>foo</p>
-</blockquote>
-
-A blank line always separates block quotes:
-> foo
-
-> bar
-.
-<blockquote>
-<p>foo</p>
-</blockquote>
-<blockquote>
-<p>bar</p>
-</blockquote>
-
-(Most current Markdown implementations, including John Gruber's
-original Markdown.pl, will parse this example as a single block quote
-with two paragraphs. But it seems better to allow the author to decide
-whether two block quotes or one are wanted.)
-Consecutiveness means that if we put these block quotes together,
-we get a single block quote:
-> foo
-> bar
-.
-<blockquote>
-<p>foo
-bar</p>
-</blockquote>
-
-To get a block quote with two paragraphs, use:
-> foo
->
-> bar
-.
-<blockquote>
-<p>foo</p>
-<p>bar</p>
-</blockquote>
-
-Block quotes can interrupt paragraphs:
-foo
-> bar
-.
-<p>foo</p>
-<blockquote>
-<p>bar</p>
-</blockquote>
-
-In general, blank lines are not needed before or after block
-quotes:
-> aaa
-***
-> bbb
-.
-<blockquote>
-<p>aaa</p>
-</blockquote>
-<hr />
-<blockquote>
-<p>bbb</p>
-</blockquote>
-
-However, because of laziness, a blank line is needed between
-a block quote and a following paragraph:
-> bar
-baz
-.
-<blockquote>
-<p>bar
-baz</p>
-</blockquote>
-
-> bar
-
-baz
-.
-<blockquote>
-<p>bar</p>
-</blockquote>
-<p>baz</p>
-
-> bar
->
-baz
-.
-<blockquote>
-<p>bar</p>
-</blockquote>
-<p>baz</p>
-
-It is a consequence of the Laziness rule that any number
-of initial >s may be omitted on a continuation line of a
-nested block quote:
-> > > foo
-bar
-.
-<blockquote>
-<blockquote>
-<blockquote>
-<p>foo
-bar</p>
-</blockquote>
-</blockquote>
-</blockquote>
-
->>> foo
-> bar
->>baz
-.
-<blockquote>
-<blockquote>
-<blockquote>
-<p>foo
-bar
-baz</p>
-</blockquote>
-</blockquote>
-</blockquote>
-
-When including an indented code block in a block quote,
-remember that the [block quote marker] includes
-both the > and a following space. So five spaces are needed after
-the >:
-> code
-
-> not code
-.
-<blockquote>
-<pre><code>code
-</code></pre>
-</blockquote>
-<blockquote>
-<p>not code</p>
-</blockquote>
-
-List items
-A list marker is a
-[bullet list marker] or an [ordered list marker].
-A bullet list marker
-is a -, +, or * character.
-An ordered list marker
-is a sequence of 1--9 arabic digits (0-9), followed by either a
-. character or a ) character. (The reason for the length
-limit is that with 10 digits we start seeing integer overflows
-in some browsers.)
-The following rules define [list items]:
-
--
-
Basic case. If a sequence of lines Ls constitute a sequence of
-blocks Bs starting with a [non-whitespace character], and M is a
-list marker of width W followed by 1 ≤ N ≤ 4 spaces, then the result
-of prepending M and the following spaces to the first line of
-Ls, and indenting subsequent lines of Ls by W + N spaces, is a
-list item with Bs as its contents. The type of the list item
-(bullet or ordered) is determined by the type of its list marker.
-If the list item is ordered, then it is also assigned a start
-number, based on the ordered list marker.
-Exceptions:
-
-- When the first list item in a [list] interrupts
-a paragraph---that is, when it starts on a line that would
-otherwise count as [paragraph continuation text]---then (a)
-the lines Ls must not begin with a blank line, and (b) if
-the list item is ordered, the start number must be 1.
-- If any line is a [thematic break][thematic breaks] then
-that line is not a list item.
-
-
-
-For example, let Ls be the lines
-A paragraph
-with two lines.
-
- indented code
-
-> A block quote.
-.
-<p>A paragraph
-with two lines.</p>
-<pre><code>indented code
-</code></pre>
-<blockquote>
-<p>A block quote.</p>
-</blockquote>
-
-And let M be the marker 1., and N = 2. Then rule #1 says
-that the following is an ordered list item with start number 1,
-and the same contents as Ls:
-1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-<ol>
-<li>
-<p>A paragraph
-with two lines.</p>
-<pre><code>indented code
-</code></pre>
-<blockquote>
-<p>A block quote.</p>
-</blockquote>
-</li>
-</ol>
-
-The most important thing to notice is that the position of
-the text after the list marker determines how much indentation
-is needed in subsequent blocks in the list item. If the list
-marker takes up two spaces, and there are three spaces between
-the list marker and the next [non-whitespace character], then blocks
-must be indented five spaces in order to fall under the list
-item.
-Here are some examples showing how far content must be indented to be
-put under the list item:
-- one
-
- two
-.
-<ul>
-<li>one</li>
-</ul>
-<p>two</p>
-
-- one
-
- two
-.
-<ul>
-<li>
-<p>one</p>
-<p>two</p>
-</li>
-</ul>
-
- - one
-
- two
-.
-<ul>
-<li>one</li>
-</ul>
-<pre><code> two
-</code></pre>
-
- - one
-
- two
-.
-<ul>
-<li>
-<p>one</p>
-<p>two</p>
-</li>
-</ul>
-
-It is tempting to think of this in terms of columns: the continuation
-blocks must be indented at least to the column of the first
-[non-whitespace character] after the list marker. However, that is not quite right.
-The spaces after the list marker determine how much relative indentation
-is needed. Which column this indentation reaches will depend on
-how the list item is embedded in other constructions, as shown by
-this example:
- > > 1. one
->>
->> two
-.
-<blockquote>
-<blockquote>
-<ol>
-<li>
-<p>one</p>
-<p>two</p>
-</li>
-</ol>
-</blockquote>
-</blockquote>
-
-Here two occurs in the same column as the list marker 1.,
-but is actually contained in the list item, because there is
-sufficient indentation after the last containing blockquote marker.
-The converse is also possible. In the following example, the word two
-occurs far to the right of the initial text of the list item, one, but
-it is not considered part of the list item, because it is not indented
-far enough past the blockquote marker:
->>- one
->>
- > > two
-.
-<blockquote>
-<blockquote>
-<ul>
-<li>one</li>
-</ul>
-<p>two</p>
-</blockquote>
-</blockquote>
-
-Note that at least one space is needed between the list marker and
-any following content, so these are not list items:
--one
-
-2.two
-.
-<p>-one</p>
-<p>2.two</p>
-
-A list item may contain blocks that are separated by more than
-one blank line.
-- foo
-
-
- bar
-.
-<ul>
-<li>
-<p>foo</p>
-<p>bar</p>
-</li>
-</ul>
-
-A list item may contain any kind of block:
-1. foo
-
- ```
- bar
- ```
-
- baz
-
- > bam
-.
-<ol>
-<li>
-<p>foo</p>
-<pre><code>bar
-</code></pre>
-<p>baz</p>
-<blockquote>
-<p>bam</p>
-</blockquote>
-</li>
-</ol>
-
-A list item that contains an indented code block will preserve
-empty lines within the code block verbatim.
-- Foo
-
- bar
-
-
- baz
-.
-<ul>
-<li>
-<p>Foo</p>
-<pre><code>bar
-
-
-baz
-</code></pre>
-</li>
-</ul>
-
-Note that ordered list start numbers must be nine digits or less:
-123456789. ok
-.
-<ol start="123456789">
-<li>ok</li>
-</ol>
-
-1234567890. not ok
-.
-<p>1234567890. not ok</p>
-
-A start number may begin with 0s:
-0. ok
-.
-<ol start="0">
-<li>ok</li>
-</ol>
-
-003. ok
-.
-<ol start="3">
-<li>ok</li>
-</ol>
-
-A start number may not be negative:
--1. not ok
-.
-<p>-1. not ok</p>
-
-
-- Item starting with indented code. If a sequence of lines Ls
-constitute a sequence of blocks Bs starting with an indented code
-block, and M is a list marker of width W followed by
-one space, then the result of prepending M and the following
-space to the first line of Ls, and indenting subsequent lines of
-Ls by W + 1 spaces, is a list item with Bs as its contents.
-If a line is empty, then it need not be indented. The type of the
-list item (bullet or ordered) is determined by the type of its list
-marker. If the list item is ordered, then it is also assigned a
-start number, based on the ordered list marker.
-
-An indented code block will have to be indented four spaces beyond
-the edge of the region where text will be included in the list item.
-In the following case that is 6 spaces:
-- foo
-
- bar
-.
-<ul>
-<li>
-<p>foo</p>
-<pre><code>bar
-</code></pre>
-</li>
-</ul>
-
-And in this case it is 11 spaces:
- 10. foo
-
- bar
-.
-<ol start="10">
-<li>
-<p>foo</p>
-<pre><code>bar
-</code></pre>
-</li>
-</ol>
-
-If the first block in the list item is an indented code block,
-then by rule #2, the contents must be indented one space after the
-list marker:
- indented code
-
-paragraph
-
- more code
-.
-<pre><code>indented code
-</code></pre>
-<p>paragraph</p>
-<pre><code>more code
-</code></pre>
-
-1. indented code
-
- paragraph
-
- more code
-.
-<ol>
-<li>
-<pre><code>indented code
-</code></pre>
-<p>paragraph</p>
-<pre><code>more code
-</code></pre>
-</li>
-</ol>
-
-Note that an additional space indent is interpreted as space
-inside the code block:
-1. indented code
-
- paragraph
-
- more code
-.
-<ol>
-<li>
-<pre><code> indented code
-</code></pre>
-<p>paragraph</p>
-<pre><code>more code
-</code></pre>
-</li>
-</ol>
-
-Note that rules #1 and #2 only apply to two cases: (a) cases
-in which the lines to be included in a list item begin with a
-[non-whitespace character], and (b) cases in which
-they begin with an indented code
-block. In a case like the following, where the first block begins with
-a three-space indent, the rules do not allow us to form a list item by
-indenting the whole thing and prepending a list marker:
- foo
-
-bar
-.
-<p>foo</p>
-<p>bar</p>
-
-- foo
-
- bar
-.
-<ul>
-<li>foo</li>
-</ul>
-<p>bar</p>
-
-This is not a significant restriction, because when a block begins
-with 1-3 spaces indent, the indentation can always be removed without
-a change in interpretation, allowing rule #1 to be applied. So, in
-the above case:
-- foo
-
- bar
-.
-<ul>
-<li>
-<p>foo</p>
-<p>bar</p>
-</li>
-</ul>
-
-
-- Item starting with a blank line. If a sequence of lines Ls
-starting with a single [blank line] constitute a (possibly empty)
-sequence of blocks Bs, not separated from each other by more than
-one blank line, and M is a list marker of width W,
-then the result of prepending M to the first line of Ls, and
-indenting subsequent lines of Ls by W + 1 spaces, is a list
-item with Bs as its contents.
-If a line is empty, then it need not be indented. The type of the
-list item (bullet or ordered) is determined by the type of its list
-marker. If the list item is ordered, then it is also assigned a
-start number, based on the ordered list marker.
-
-Here are some list items that start with a blank line but are not empty:
--
- foo
--
- ```
- bar
- ```
--
- baz
-.
-<ul>
-<li>foo</li>
-<li>
-<pre><code>bar
-</code></pre>
-</li>
-<li>
-<pre><code>baz
-</code></pre>
-</li>
-</ul>
-
-When the list item starts with a blank line, the number of spaces
-following the list marker doesn't change the required indentation:
--
- foo
-.
-<ul>
-<li>foo</li>
-</ul>
-
-A list item can begin with at most one blank line.
-In the following example, foo is not part of the list
-item:
--
-
- foo
-.
-<ul>
-<li></li>
-</ul>
-<p>foo</p>
-
-Here is an empty bullet list item:
-- foo
--
-- bar
-.
-<ul>
-<li>foo</li>
-<li></li>
-<li>bar</li>
-</ul>
-
-It does not matter whether there are spaces following the [list marker]:
-- foo
--
-- bar
-.
-<ul>
-<li>foo</li>
-<li></li>
-<li>bar</li>
-</ul>
-
-Here is an empty ordered list item:
-1. foo
-2.
-3. bar
-.
-<ol>
-<li>foo</li>
-<li></li>
-<li>bar</li>
-</ol>
-
-A list may start or end with an empty list item:
-*
-.
-<ul>
-<li></li>
-</ul>
-
-However, an empty list item cannot interrupt a paragraph:
-foo
-*
-
-foo
-1.
-.
-<p>foo
-*</p>
-<p>foo
-1.</p>
-
-
-- Indentation. If a sequence of lines Ls constitutes a list item
-according to rule #1, #2, or #3, then the result of indenting each line
-of Ls by 1-3 spaces (the same for each line) also constitutes a
-list item with the same contents and attributes. If a line is
-empty, then it need not be indented.
-
-Indented one space:
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-<ol>
-<li>
-<p>A paragraph
-with two lines.</p>
-<pre><code>indented code
-</code></pre>
-<blockquote>
-<p>A block quote.</p>
-</blockquote>
-</li>
-</ol>
-
-Indented two spaces:
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-<ol>
-<li>
-<p>A paragraph
-with two lines.</p>
-<pre><code>indented code
-</code></pre>
-<blockquote>
-<p>A block quote.</p>
-</blockquote>
-</li>
-</ol>
-
-Indented three spaces:
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-<ol>
-<li>
-<p>A paragraph
-with two lines.</p>
-<pre><code>indented code
-</code></pre>
-<blockquote>
-<p>A block quote.</p>
-</blockquote>
-</li>
-</ol>
-
-Four spaces indent gives a code block:
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-<pre><code>1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-</code></pre>
-
-
-- Laziness. If a string of lines Ls constitute a list
-item with contents Bs, then the result of deleting
-some or all of the indentation from one or more lines in which the
-next [non-whitespace character] after the indentation is
-[paragraph continuation text] is a
-list item with the same contents and attributes. The unindented
-lines are called
-lazy continuation lines.
-
-Here is an example with [lazy continuation lines]:
- 1. A paragraph
-with two lines.
-
- indented code
-
- > A block quote.
-.
-<ol>
-<li>
-<p>A paragraph
-with two lines.</p>
-<pre><code>indented code
-</code></pre>
-<blockquote>
-<p>A block quote.</p>
-</blockquote>
-</li>
-</ol>
-
-Indentation can be partially deleted:
- 1. A paragraph
- with two lines.
-.
-<ol>
-<li>A paragraph
-with two lines.</li>
-</ol>
-
-These examples show how laziness can work in nested structures:
-> 1. > Blockquote
-continued here.
-.
-<blockquote>
-<ol>
-<li>
-<blockquote>
-<p>Blockquote
-continued here.</p>
-</blockquote>
-</li>
-</ol>
-</blockquote>
-
-> 1. > Blockquote
-> continued here.
-.
-<blockquote>
-<ol>
-<li>
-<blockquote>
-<p>Blockquote
-continued here.</p>
-</blockquote>
-</li>
-</ol>
-</blockquote>
-
-
-- That's all. Nothing that is not counted as a list item by rules
-#1--5 counts as a list item.
-
-The rules for sublists follow from the general rules
-[above][List items]. A sublist must be indented the same number
-of spaces a paragraph would need to be in order to be included
-in the list item.
-So, in this case we need two spaces indent:
-- foo
- - bar
- - baz
- - boo
-.
-<ul>
-<li>foo
-<ul>
-<li>bar
-<ul>
-<li>baz
-<ul>
-<li>boo</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-
-One is not enough:
-- foo
- - bar
- - baz
- - boo
-.
-<ul>
-<li>foo</li>
-<li>bar</li>
-<li>baz</li>
-<li>boo</li>
-</ul>
-
-Here we need four, because the list marker is wider:
-10) foo
- - bar
-.
-<ol start="10">
-<li>foo
-<ul>
-<li>bar</li>
-</ul>
-</li>
-</ol>
-
-Three is not enough:
-10) foo
- - bar
-.
-<ol start="10">
-<li>foo</li>
-</ol>
-<ul>
-<li>bar</li>
-</ul>
-
-A list may be the first block in a list item:
-- - foo
-.
-<ul>
-<li>
-<ul>
-<li>foo</li>
-</ul>
-</li>
-</ul>
-
-1. - 2. foo
-.
-<ol>
-<li>
-<ul>
-<li>
-<ol start="2">
-<li>foo</li>
-</ol>
-</li>
-</ul>
-</li>
-</ol>
-
-A list item can contain a heading:
-- # Foo
-- Bar
- ---
- baz
-.
-<ul>
-<li>
-<h1>Foo</h1>
-</li>
-<li>
-<h2>Bar</h2>
-baz</li>
-</ul>
-
-Motivation
-John Gruber's Markdown spec says the following about list items:
-
--
-
"List markers typically start at the left margin, but may be indented
-by up to three spaces. List markers must be followed by one or more
-spaces or a tab."
-
--
-
"To make lists look nice, you can wrap items with hanging indents....
-But if you don't want to, you don't have to."
-
--
-
"List items may consist of multiple paragraphs. Each subsequent
-paragraph in a list item must be indented by either 4 spaces or one
-tab."
-
--
-
"It looks nice if you indent every line of the subsequent paragraphs,
-but here again, Markdown will allow you to be lazy."
-
--
-
"To put a blockquote within a list item, the blockquote's >
-delimiters need to be indented."
-
--
-
"To put a code block within a list item, the code block needs to be
-indented twice — 8 spaces or two tabs."
-
-
-These rules specify that a paragraph under a list item must be indented
-four spaces (presumably, from the left margin, rather than the start of
-the list marker, but this is not said), and that code under a list item
-must be indented eight spaces instead of the usual four. They also say
-that a block quote must be indented, but not by how much; however, the
-example given has four spaces indentation. Although nothing is said
-about other kinds of block-level content, it is certainly reasonable to
-infer that all block elements under a list item, including other
-lists, must be indented four spaces. This principle has been called the
-four-space rule.
-The four-space rule is clear and principled, and if the reference
-implementation Markdown.pl had followed it, it probably would have
-become the standard. However, Markdown.pl allowed paragraphs and
-sublists to start with only two spaces indentation, at least on the
-outer level. Worse, its behavior was inconsistent: a sublist of an
-outer-level list needed two spaces indentation, but a sublist of this
-sublist needed three spaces. It is not surprising, then, that different
-implementations of Markdown have developed very different rules for
-determining what comes under a list item. (Pandoc and python-Markdown,
-for example, stuck with Gruber's syntax description and the four-space
-rule, while discount, redcarpet, marked, PHP Markdown, and others
-followed Markdown.pl's behavior more closely.)
-Unfortunately, given the divergences between implementations, there
-is no way to give a spec for list items that will be guaranteed not
-to break any existing documents. However, the spec given here should
-correctly handle lists formatted with either the four-space rule or
-the more forgiving Markdown.pl behavior, provided they are laid out
-in a way that is natural for a human to read.
-The strategy here is to let the width and indentation of the list marker
-determine the indentation necessary for blocks to fall under the list
-item, rather than having a fixed and arbitrary number. The writer can
-think of the body of the list item as a unit which gets indented to the
-right enough to fit the list marker (and any indentation on the list
-marker). (The laziness rule, #5, then allows continuation lines to be
-unindented if needed.)
-This rule is superior, we claim, to any rule requiring a fixed level of
-indentation from the margin. The four-space rule is clear but
-unnatural. It is quite unintuitive that
-- foo
-
- bar
-
- - baz
-
-should be parsed as two lists with an intervening paragraph,
-<ul>
-<li>foo</li>
-</ul>
-<p>bar</p>
-<ul>
-<li>baz</li>
-</ul>
-
-as the four-space rule demands, rather than a single list,
-<ul>
-<li>
-<p>foo</p>
-<p>bar</p>
-<ul>
-<li>baz</li>
-</ul>
-</li>
-</ul>
-
-The choice of four spaces is arbitrary. It can be learned, but it is
-not likely to be guessed, and it trips up beginners regularly.
-Would it help to adopt a two-space rule? The problem is that such
-a rule, together with the rule allowing 1--3 spaces indentation of the
-initial list marker, allows text that is indented less than the
-original list marker to be included in the list item. For example,
-Markdown.pl parses
- - one
-
- two
-
-as a single list item, with two a continuation paragraph:
-<ul>
-<li>
-<p>one</p>
-<p>two</p>
-</li>
-</ul>
-
-and similarly
-> - one
->
-> two
-
-as
-<blockquote>
-<ul>
-<li>
-<p>one</p>
-<p>two</p>
-</li>
-</ul>
-</blockquote>
-
-This is extremely unintuitive.
-Rather than requiring a fixed indent from the margin, we could require
-a fixed indent (say, two spaces, or even one space) from the list marker (which
-may itself be indented). This proposal would remove the last anomaly
-discussed. Unlike the spec presented above, it would count the following
-as a list item with a subparagraph, even though the paragraph bar
-is not indented as far as the first paragraph foo:
- 10. foo
-
- bar
-
-Arguably this text does read like a list item with bar as a subparagraph,
-which may count in favor of the proposal. However, on this proposal indented
-code would have to be indented six spaces after the list marker. And this
-would break a lot of existing Markdown, which has the pattern:
-1. foo
-
- indented code
-
-where the code is indented eight spaces. The spec above, by contrast, will
-parse this text as expected, since the code block's indentation is measured
-from the beginning of foo.
-The one case that needs special treatment is a list item that starts
-with indented code. How much indentation is required in that case, since
-we don't have a "first paragraph" to measure from? Rule #2 simply stipulates
-that in such cases, we require one space indentation from the list marker
-(and then the normal four spaces for the indented code). This will match the
-four-space rule in cases where the list marker plus its initial indentation
-takes four spaces (a common case), but diverge in other cases.
-Lists
-A list is a sequence of one or more
-list items [of the same type]. The list items
-may be separated by any number of blank lines.
-Two list items are of the same type
-if they begin with a [list marker] of the same type.
-Two list markers are of the
-same type if (a) they are bullet list markers using the same character
-(-, +, or *) or (b) they are ordered list numbers with the same
-delimiter (either . or )).
-A list is an ordered list
-if its constituent list items begin with
-[ordered list markers], and a
-bullet list if its constituent list
-items begin with [bullet list markers].
-The start number
-of an [ordered list] is determined by the list number of
-its initial list item. The numbers of subsequent list items are
-disregarded.
-A list is loose if any of its constituent
-list items are separated by blank lines, or if any of its constituent
-list items directly contain two block-level elements with a blank line
-between them. Otherwise a list is tight.
-(The difference in HTML output is that paragraphs in a loose list are
-wrapped in <p> tags, while paragraphs in a tight list are not.)
-Changing the bullet or ordered list delimiter starts a new list:
-- foo
-- bar
-+ baz
-.
-<ul>
-<li>foo</li>
-<li>bar</li>
-</ul>
-<ul>
-<li>baz</li>
-</ul>
-
-1. foo
-2. bar
-3) baz
-.
-<ol>
-<li>foo</li>
-<li>bar</li>
-</ol>
-<ol start="3">
-<li>baz</li>
-</ol>
-
-In CommonMark, a list can interrupt a paragraph. That is,
-no blank line is needed to separate a paragraph from a following
-list:
-Foo
-- bar
-- baz
-.
-<p>Foo</p>
-<ul>
-<li>bar</li>
-<li>baz</li>
-</ul>
-
-Markdown.pl does not allow this, through fear of triggering a list
-via a numeral in a hard-wrapped line:
-The number of windows in my house is
-14. The number of doors is 6.
-
-Oddly, though, Markdown.pl does allow a blockquote to
-interrupt a paragraph, even though the same considerations might
-apply.
-In CommonMark, we do allow lists to interrupt paragraphs, for
-two reasons. First, it is natural and not uncommon for people
-to start lists without blank lines:
-I need to buy
-- new shoes
-- a coat
-- a plane ticket
-
-Second, we are attracted to a
-
-principle of uniformity:
-if a chunk of text has a certain
-meaning, it will continue to have the same meaning when put into a
-container block (such as a list item or blockquote).
-
-(Indeed, the spec for [list items] and [block quotes] presupposes
-this principle.) This principle implies that if
- * I need to buy
- - new shoes
- - a coat
- - a plane ticket
-
-is a list item containing a paragraph followed by a nested sublist,
-as all Markdown implementations agree it is (though the paragraph
-may be rendered without <p> tags, since the list is "tight"),
-then
-I need to buy
-- new shoes
-- a coat
-- a plane ticket
-
-by itself should be a paragraph followed by a nested sublist.
-Since it is well established Markdown practice to allow lists to
-interrupt paragraphs inside list items, the [principle of
-uniformity] requires us to allow this outside list items as
-well. (reStructuredText
-takes a different approach, requiring blank lines before lists
-even inside other list items.)
-In order to solve of unwanted lists in paragraphs with
-hard-wrapped numerals, we allow only lists starting with 1 to
-interrupt paragraphs. Thus,
-The number of windows in my house is
-14. The number of doors is 6.
-.
-<p>The number of windows in my house is
-14. The number of doors is 6.</p>
-
-We may still get an unintended result in cases like
-The number of windows in my house is
-1. The number of doors is 6.
-.
-<p>The number of windows in my house is</p>
-<ol>
-<li>The number of doors is 6.</li>
-</ol>
-
-but this rule should prevent most spurious list captures.
-There can be any number of blank lines between items:
-- foo
-
-- bar
-
-
-- baz
-.
-<ul>
-<li>
-<p>foo</p>
-</li>
-<li>
-<p>bar</p>
-</li>
-<li>
-<p>baz</p>
-</li>
-</ul>
-
-- foo
- - bar
- - baz
-
-
- bim
-.
-<ul>
-<li>foo
-<ul>
-<li>bar
-<ul>
-<li>
-<p>baz</p>
-<p>bim</p>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-
-To separate consecutive lists of the same type, or to separate a
-list from an indented code block that would otherwise be parsed
-as a subparagraph of the final list item, you can insert a blank HTML
-comment:
-- foo
-- bar
-
-<!-- -->
-
-- baz
-- bim
-.
-<ul>
-<li>foo</li>
-<li>bar</li>
-</ul>
-<!-- -->
-<ul>
-<li>baz</li>
-<li>bim</li>
-</ul>
-
-- foo
-
- notcode
-
-- foo
-
-<!-- -->
-
- code
-.
-<ul>
-<li>
-<p>foo</p>
-<p>notcode</p>
-</li>
-<li>
-<p>foo</p>
-</li>
-</ul>
-<!-- -->
-<pre><code>code
-</code></pre>
-
-List items need not be indented to the same level. The following
-list items will be treated as items at the same list level,
-since none is indented enough to belong to the previous list
-item:
-- a
- - b
- - c
- - d
- - e
- - f
-- g
-.
-<ul>
-<li>a</li>
-<li>b</li>
-<li>c</li>
-<li>d</li>
-<li>e</li>
-<li>f</li>
-<li>g</li>
-</ul>
-
-1. a
-
- 2. b
-
- 3. c
-.
-<ol>
-<li>
-<p>a</p>
-</li>
-<li>
-<p>b</p>
-</li>
-<li>
-<p>c</p>
-</li>
-</ol>
-
-Note, however, that list items may not be indented more than
-three spaces. Here - e is treated as a paragraph continuation
-line, because it is indented more than three spaces:
-- a
- - b
- - c
- - d
- - e
-.
-<ul>
-<li>a</li>
-<li>b</li>
-<li>c</li>
-<li>d
-- e</li>
-</ul>
-
-And here, 3. c is treated as in indented code block,
-because it is indented four spaces and preceded by a
-blank line.
-1. a
-
- 2. b
-
- 3. c
-.
-<ol>
-<li>
-<p>a</p>
-</li>
-<li>
-<p>b</p>
-</li>
-</ol>
-<pre><code>3. c
-</code></pre>
-
-This is a loose list, because there is a blank line between
-two of the list items:
-- a
-- b
-
-- c
-.
-<ul>
-<li>
-<p>a</p>
-</li>
-<li>
-<p>b</p>
-</li>
-<li>
-<p>c</p>
-</li>
-</ul>
-
-So is this, with a empty second item:
-* a
-*
-
-* c
-.
-<ul>
-<li>
-<p>a</p>
-</li>
-<li></li>
-<li>
-<p>c</p>
-</li>
-</ul>
-
-These are loose lists, even though there is no space between the items,
-because one of the items directly contains two block-level elements
-with a blank line between them:
-- a
-- b
-
- c
-- d
-.
-<ul>
-<li>
-<p>a</p>
-</li>
-<li>
-<p>b</p>
-<p>c</p>
-</li>
-<li>
-<p>d</p>
-</li>
-</ul>
-
-- a
-- b
-
- [ref]: /url
-- d
-.
-<ul>
-<li>
-<p>a</p>
-</li>
-<li>
-<p>b</p>
-</li>
-<li>
-<p>d</p>
-</li>
-</ul>
-
-This is a tight list, because the blank lines are in a code block:
-- a
-- ```
- b
-
-
- ```
-- c
-.
-<ul>
-<li>a</li>
-<li>
-<pre><code>b
-
-
-</code></pre>
-</li>
-<li>c</li>
-</ul>
-
-This is a tight list, because the blank line is between two
-paragraphs of a sublist. So the sublist is loose while
-the outer list is tight:
-- a
- - b
-
- c
-- d
-.
-<ul>
-<li>a
-<ul>
-<li>
-<p>b</p>
-<p>c</p>
-</li>
-</ul>
-</li>
-<li>d</li>
-</ul>
-
-This is a tight list, because the blank line is inside the
-block quote:
-* a
- > b
- >
-* c
-.
-<ul>
-<li>a
-<blockquote>
-<p>b</p>
-</blockquote>
-</li>
-<li>c</li>
-</ul>
-
-This list is tight, because the consecutive block elements
-are not separated by blank lines:
-- a
- > b
- ```
- c
- ```
-- d
-.
-<ul>
-<li>a
-<blockquote>
-<p>b</p>
-</blockquote>
-<pre><code>c
-</code></pre>
-</li>
-<li>d</li>
-</ul>
-
-A single-paragraph list is tight:
-- a
-.
-<ul>
-<li>a</li>
-</ul>
-
-- a
- - b
-.
-<ul>
-<li>a
-<ul>
-<li>b</li>
-</ul>
-</li>
-</ul>
-
-This list is loose, because of the blank line between the
-two block elements in the list item:
-1. ```
- foo
- ```
-
- bar
-.
-<ol>
-<li>
-<pre><code>foo
-</code></pre>
-<p>bar</p>
-</li>
-</ol>
-
-Here the outer list is loose, the inner list tight:
-* foo
- * bar
-
- baz
-.
-<ul>
-<li>
-<p>foo</p>
-<ul>
-<li>bar</li>
-</ul>
-<p>baz</p>
-</li>
-</ul>
-
-- a
- - b
- - c
-
-- d
- - e
- - f
-.
-<ul>
-<li>
-<p>a</p>
-<ul>
-<li>b</li>
-<li>c</li>
-</ul>
-</li>
-<li>
-<p>d</p>
-<ul>
-<li>e</li>
-<li>f</li>
-</ul>
-</li>
-</ul>
-
-Inlines
-Inlines are parsed sequentially from the beginning of the character
-stream to the end (left to right, in left-to-right languages).
-Thus, for example, in
-`hi`lo`
-.
-<p><code>hi</code>lo`</p>
-
-hi is parsed as code, leaving the backtick at the end as a literal
-backtick.
-Backslash escapes
-Any ASCII punctuation character may be backslash-escaped:
-\!\"\#\$\%\&\'\(\)\*\+\,\-\.\/\:\;\<\=\>\?\@\[\\\]\^\_\`\{\|\}\~
-.
-<p>!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~</p>
-
-Backslashes before other characters are treated as literal
-backslashes:
-\→\A\a\ \3\φ\«
-.
-<p>\→\A\a\ \3\φ\«</p>
-
-Escaped characters are treated as regular characters and do
-not have their usual Markdown meanings:
-\*not emphasized*
-\<br/> not a tag
-\[not a link](/foo)
-\`not code`
-1\. not a list
-\* not a list
-\# not a heading
-\[foo]: /url "not a reference"
-\ö not a character entity
-.
-<p>*not emphasized*
-<br/> not a tag
-[not a link](/foo)
-`not code`
-1. not a list
-* not a list
-# not a heading
-[foo]: /url "not a reference"
-&ouml; not a character entity</p>
-
-If a backslash is itself escaped, the following character is not:
-\\*emphasis*
-.
-<p>\<em>emphasis</em></p>
-
-A backslash at the end of the line is a [hard line break]:
-foo\
-bar
-.
-<p>foo<br />
-bar</p>
-
-Backslash escapes do not work in code blocks, code spans, autolinks, or
-raw HTML:
-`` \[\` ``
-.
-<p><code>\[\`</code></p>
-
- \[\]
-.
-<pre><code>\[\]
-</code></pre>
-
-~~~
-\[\]
-~~~
-.
-<pre><code>\[\]
-</code></pre>
-
-<http://example.com?find=\*>
-.
-<p><a href="http://example.com?find=%5C*">http://example.com?find=\*</a></p>
-
-<a href="/bar\/)">
-.
-<a href="/bar\/)">
-
-But they work in all other contexts, including URLs and link titles,
-link references, and [info strings] in [fenced code blocks]:
-[foo](/bar\* "ti\*tle")
-.
-<p><a href="/bar*" title="ti*tle">foo</a></p>
-
-[foo]
-
-[foo]: /bar\* "ti\*tle"
-.
-<p><a href="/bar*" title="ti*tle">foo</a></p>
-
-``` foo\+bar
-foo
-```
-.
-<pre><code class="language-foo+bar">foo
-</code></pre>
-
-Entity and numeric character references
-Valid HTML entity references and numeric character references
-can be used in place of the corresponding Unicode character,
-with the following exceptions:
-
--
-
Entity and character references are not recognized in code
-blocks and code spans.
-
--
-
Entity and character references cannot stand in place of
-special characters that define structural elements in
-CommonMark. For example, although * can be used
-in place of a literal * character, * cannot replace
-* in emphasis delimiters, bullet list markers, or thematic
-breaks.
-
-
-Conforming CommonMark parsers need not store information about
-whether a particular character was represented in the source
-using a Unicode character or an entity reference.
-Entity references consist of & + any of the valid
-HTML5 entity names + ;. The
-document https://html.spec.whatwg.org/multipage/entities.json
-is used as an authoritative source for the valid entity
-references and their corresponding code points.
- & © Æ Ď
-¾ ℋ ⅆ
-∲ ≧̸
-.
-<p> & © Æ Ď
-¾ ℋ ⅆ
-∲ ≧̸</p>
-
-Decimal numeric character
-references
-consist of &# + a string of 1--7 arabic digits + ;. A
-numeric character reference is parsed as the corresponding
-Unicode character. Invalid Unicode code points will be replaced by
-the REPLACEMENT CHARACTER (U+FFFD). For security reasons,
-the code point U+0000 will also be replaced by U+FFFD.
-# Ӓ Ϡ �
-.
-<p># Ӓ Ϡ �</p>
-
-Hexadecimal numeric character
-references consist of &# +
-either X or x + a string of 1-6 hexadecimal digits + ;.
-They too are parsed as the corresponding Unicode character (this
-time specified with a hexadecimal numeral instead of decimal).
-" ആ ಫ
-.
-<p>" ആ ಫ</p>
-
-Here are some nonentities:
-  &x; &#; &#x;
-�
-&#abcdef0;
-&ThisIsNotDefined; &hi?;
-.
-<p>&nbsp &x; &#; &#x;
-&#987654321;
-&#abcdef0;
-&ThisIsNotDefined; &hi?;</p>
-
-Although HTML5 does accept some entity references
-without a trailing semicolon (such as ©), these are not
-recognized here, because it makes the grammar too ambiguous:
-©
-.
-<p>&copy</p>
-
-Strings that are not on the list of HTML5 named entities are not
-recognized as entity references either:
-&MadeUpEntity;
-.
-<p>&MadeUpEntity;</p>
-
-Entity and numeric character references are recognized in any
-context besides code spans or code blocks, including
-URLs, [link titles], and [fenced code block][] [info strings]:
-<a href="öö.html">
-.
-<a href="öö.html">
-
-[foo](/föö "föö")
-.
-<p><a href="/f%C3%B6%C3%B6" title="föö">foo</a></p>
-
-[foo]
-
-[foo]: /föö "föö"
-.
-<p><a href="/f%C3%B6%C3%B6" title="föö">foo</a></p>
-
-``` föö
-foo
-```
-.
-<pre><code class="language-föö">foo
-</code></pre>
-
-Entity and numeric character references are treated as literal
-text in code spans and code blocks:
-`föö`
-.
-<p><code>f&ouml;&ouml;</code></p>
-
- föfö
-.
-<pre><code>f&ouml;f&ouml;
-</code></pre>
-
-Entity and numeric character references cannot be used
-in place of symbols indicating structure in CommonMark
-documents.
-*foo*
-*foo*
-.
-<p>*foo*
-<em>foo</em></p>
-
-* foo
-
-* foo
-.
-<p>* foo</p>
-<ul>
-<li>foo</li>
-</ul>
-
-foo bar
-.
-<p>foo
-
-bar</p>
-
-	foo
-.
-<p>→foo</p>
-
-[a](url "tit")
-.
-<p>[a](url "tit")</p>
-
-Code spans
-A backtick string
-is a string of one or more backtick characters (`) that is neither
-preceded nor followed by a backtick.
-A code span begins with a backtick string and ends with
-a backtick string of equal length. The contents of the code span are
-the characters between the two backtick strings, normalized in the
-following ways:
-
-- First, [line endings] are converted to [spaces].
-- If the resulting string both begins and ends with a [space]
-character, but does not consist entirely of [space]
-characters, a single [space] character is removed from the
-front and back. This allows you to include code that begins
-or ends with backtick characters, which must be separated by
-whitespace from the opening or closing backtick strings.
-
-This is a simple code span:
-`foo`
-.
-<p><code>foo</code></p>
-
-Here two backticks are used, because the code contains a backtick.
-This example also illustrates stripping of a single leading and
-trailing space:
-`` foo ` bar ``
-.
-<p><code>foo ` bar</code></p>
-
-This example shows the motivation for stripping leading and trailing
-spaces:
-` `` `
-.
-<p><code>``</code></p>
-
-Note that only one space is stripped:
-` `` `
-.
-<p><code> `` </code></p>
-
-The stripping only happens if the space is on both
-sides of the string:
-` a`
-.
-<p><code> a</code></p>
-
-Only [spaces], and not [unicode whitespace] in general, are
-stripped in this way:
-` b `
-.
-<p><code> b </code></p>
-
-No stripping occurs if the code span contains only spaces:
-` `
-` `
-.
-<p><code> </code>
-<code> </code></p>
-
-[Line endings] are treated like spaces:
-``
-foo
-bar
-baz
-``
-.
-<p><code>foo bar baz</code></p>
-
-``
-foo
-``
-.
-<p><code>foo </code></p>
-
-Interior spaces are not collapsed:
-`foo bar
-baz`
-.
-<p><code>foo bar baz</code></p>
-
-Note that browsers will typically collapse consecutive spaces
-when rendering <code> elements, so it is recommended that
-the following CSS be used:
-code{white-space: pre-wrap;}
-
-Note that backslash escapes do not work in code spans. All backslashes
-are treated literally:
-`foo\`bar`
-.
-<p><code>foo\</code>bar`</p>
-
-Backslash escapes are never needed, because one can always choose a
-string of n backtick characters as delimiters, where the code does
-not contain any strings of exactly n backtick characters.
-``foo`bar``
-.
-<p><code>foo`bar</code></p>
-
-` foo `` bar `
-.
-<p><code>foo `` bar</code></p>
-
-Code span backticks have higher precedence than any other inline
-constructs except HTML tags and autolinks. Thus, for example, this is
-not parsed as emphasized text, since the second * is part of a code
-span:
-*foo`*`
-.
-<p>*foo<code>*</code></p>
-
-And this is not parsed as a link:
-[not a `link](/foo`)
-.
-<p>[not a <code>link](/foo</code>)</p>
-
-Code spans, HTML tags, and autolinks have the same precedence.
-Thus, this is code:
-`<a href="`">`
-.
-<p><code><a href="</code>">`</p>
-
-But this is an HTML tag:
-<a href="`">`
-.
-<p><a href="`">`</p>
-
-And this is code:
-`<http://foo.bar.`baz>`
-.
-<p><code><http://foo.bar.</code>baz>`</p>
-
-But this is an autolink:
-<http://foo.bar.`baz>`
-.
-<p><a href="http://foo.bar.%60baz">http://foo.bar.`baz</a>`</p>
-
-When a backtick string is not closed by a matching backtick string,
-we just have literal backticks:
-```foo``
-.
-<p>```foo``</p>
-
-`foo
-.
-<p>`foo</p>
-
-The following case also illustrates the need for opening and
-closing backtick strings to be equal in length:
-`foo``bar``
-.
-<p>`foo<code>bar</code></p>
-
-Emphasis and strong emphasis
-John Gruber's original Markdown syntax
-description says:
-
-Markdown treats asterisks (*) and underscores (_) as indicators of
-emphasis. Text wrapped with one * or _ will be wrapped with an HTML
-<em> tag; double *'s or _'s will be wrapped with an HTML <strong>
-tag.
-
-This is enough for most users, but these rules leave much undecided,
-especially when it comes to nested emphasis. The original
-Markdown.pl test suite makes it clear that triple *** and
-___ delimiters can be used for strong emphasis, and most
-implementations have also allowed the following patterns:
-***strong emph***
-***strong** in emph*
-***emph* in strong**
-**in strong *emph***
-*in emph **strong***
-
-The following patterns are less widely supported, but the intent
-is clear and they are useful (especially in contexts like bibliography
-entries):
-*emph *with emph* in it*
-**strong **with strong** in it**
-
-Many implementations have also restricted intraword emphasis to
-the * forms, to avoid unwanted emphasis in words containing
-internal underscores. (It is best practice to put these in code
-spans, but users often do not.)
-internal emphasis: foo*bar*baz
-no emphasis: foo_bar_baz
-
-The rules given below capture all of these patterns, while allowing
-for efficient parsing strategies that do not backtrack.
-First, some definitions. A delimiter run is either
-a sequence of one or more * characters that is not preceded or
-followed by a non-backslash-escaped * character, or a sequence
-of one or more _ characters that is not preceded or followed by
-a non-backslash-escaped _ character.
-A left-flanking delimiter run is
-a [delimiter run] that is (1) not followed by [Unicode whitespace],
-and either (2a) not followed by a [punctuation character], or
-(2b) followed by a [punctuation character] and
-preceded by [Unicode whitespace] or a [punctuation character].
-For purposes of this definition, the beginning and the end of
-the line count as Unicode whitespace.
-A right-flanking delimiter run is
-a [delimiter run] that is (1) not preceded by [Unicode whitespace],
-and either (2a) not preceded by a [punctuation character], or
-(2b) preceded by a [punctuation character] and
-followed by [Unicode whitespace] or a [punctuation character].
-For purposes of this definition, the beginning and the end of
-the line count as Unicode whitespace.
-Here are some examples of delimiter runs.
-
--
-
left-flanking but not right-flanking:
-***abc
- _abc
-**"abc"
- _"abc"
-
-
--
-
right-flanking but not left-flanking:
- abc***
- abc_
-"abc"**
-"abc"_
-
-
--
-
Both left and right-flanking:
- abc***def
-"abc"_"def"
-
-
--
-
Neither left nor right-flanking:
-abc *** def
-a _ b
-
-
-
-(The idea of distinguishing left-flanking and right-flanking
-delimiter runs based on the character before and the character
-after comes from Roopesh Chander's
-vfmd.
-vfmd uses the terminology "emphasis indicator string" instead of "delimiter
-run," and its rules for distinguishing left- and right-flanking runs
-are a bit more complex than the ones given here.)
-The following rules define emphasis and strong emphasis:
-
--
-
A single * character can open emphasis
-iff (if and only if) it is part of a [left-flanking delimiter run].
-
--
-
A single _ character [can open emphasis] iff
-it is part of a [left-flanking delimiter run]
-and either (a) not part of a [right-flanking delimiter run]
-or (b) part of a [right-flanking delimiter run]
-preceded by punctuation.
-
--
-
A single * character can close emphasis
-iff it is part of a [right-flanking delimiter run].
-
--
-
A single _ character [can close emphasis] iff
-it is part of a [right-flanking delimiter run]
-and either (a) not part of a [left-flanking delimiter run]
-or (b) part of a [left-flanking delimiter run]
-followed by punctuation.
-
--
-
A double ** can open strong emphasis
-iff it is part of a [left-flanking delimiter run].
-
--
-
A double __ [can open strong emphasis] iff
-it is part of a [left-flanking delimiter run]
-and either (a) not part of a [right-flanking delimiter run]
-or (b) part of a [right-flanking delimiter run]
-preceded by punctuation.
-
--
-
A double ** can close strong emphasis
-iff it is part of a [right-flanking delimiter run].
-
--
-
A double __ [can close strong emphasis] iff
-it is part of a [right-flanking delimiter run]
-and either (a) not part of a [left-flanking delimiter run]
-or (b) part of a [left-flanking delimiter run]
-followed by punctuation.
-
--
-
Emphasis begins with a delimiter that [can open emphasis] and ends
-with a delimiter that [can close emphasis], and that uses the same
-character (_ or *) as the opening delimiter. The
-opening and closing delimiters must belong to separate
-[delimiter runs]. If one of the delimiters can both
-open and close emphasis, then the sum of the lengths of the
-delimiter runs containing the opening and closing delimiters
-must not be a multiple of 3 unless both lengths are
-multiples of 3.
-
--
-
Strong emphasis begins with a delimiter that
-[can open strong emphasis] and ends with a delimiter that
-[can close strong emphasis], and that uses the same character
-(_ or *) as the opening delimiter. The
-opening and closing delimiters must belong to separate
-[delimiter runs]. If one of the delimiters can both open
-and close strong emphasis, then the sum of the lengths of
-the delimiter runs containing the opening and closing
-delimiters must not be a multiple of 3 unless both lengths
-are multiples of 3.
-
--
-
A literal * character cannot occur at the beginning or end of
-*-delimited emphasis or **-delimited strong emphasis, unless it
-is backslash-escaped.
-
--
-
A literal _ character cannot occur at the beginning or end of
-_-delimited emphasis or __-delimited strong emphasis, unless it
-is backslash-escaped.
-
-
-Where rules 1--12 above are compatible with multiple parsings,
-the following principles resolve ambiguity:
-
--
-
The number of nestings should be minimized. Thus, for example,
-an interpretation <strong>...</strong> is always preferred to
-<em><em>...</em></em>.
-
--
-
An interpretation <em><strong>...</strong></em> is always
-preferred to <strong><em>...</em></strong>.
-
--
-
When two potential emphasis or strong emphasis spans overlap,
-so that the second begins before the first ends and ends after
-the first ends, the first takes precedence. Thus, for example,
-*foo _bar* baz_ is parsed as <em>foo _bar</em> baz_ rather
-than *foo <em>bar* baz</em>.
-
--
-
When there are two potential emphasis or strong emphasis spans
-with the same closing delimiter, the shorter one (the one that
-opens later) takes precedence. Thus, for example,
-**foo **bar baz** is parsed as **foo <strong>bar baz</strong>
-rather than <strong>foo **bar baz</strong>.
-
--
-
Inline code spans, links, images, and HTML tags group more tightly
-than emphasis. So, when there is a choice between an interpretation
-that contains one of these elements and one that does not, the
-former always wins. Thus, for example, *[foo*](bar) is
-parsed as *<a href="bar">foo*</a> rather than as
-<em>[foo</em>](bar).
-
-
-These rules can be illustrated through a series of examples.
-Rule 1:
-*foo bar*
-.
-<p><em>foo bar</em></p>
-
-This is not emphasis, because the opening * is followed by
-whitespace, and hence not part of a [left-flanking delimiter run]:
-a * foo bar*
-.
-<p>a * foo bar*</p>
-
-This is not emphasis, because the opening * is preceded
-by an alphanumeric and followed by punctuation, and hence
-not part of a [left-flanking delimiter run]:
-a*"foo"*
-.
-<p>a*"foo"*</p>
-
-Unicode nonbreaking spaces count as whitespace, too:
-* a *
-.
-<p>* a *</p>
-
-Intraword emphasis with * is permitted:
-foo*bar*
-.
-<p>foo<em>bar</em></p>
-
-5*6*78
-.
-<p>5<em>6</em>78</p>
-
-Rule 2:
-_foo bar_
-.
-<p><em>foo bar</em></p>
-
-This is not emphasis, because the opening _ is followed by
-whitespace:
-_ foo bar_
-.
-<p>_ foo bar_</p>
-
-This is not emphasis, because the opening _ is preceded
-by an alphanumeric and followed by punctuation:
-a_"foo"_
-.
-<p>a_"foo"_</p>
-
-Emphasis with _ is not allowed inside words:
-foo_bar_
-.
-<p>foo_bar_</p>
-
-5_6_78
-.
-<p>5_6_78</p>
-
-пристаням_стремятся_
-.
-<p>пристаням_стремятся_</p>
-
-Here _ does not generate emphasis, because the first delimiter run
-is right-flanking and the second left-flanking:
-aa_"bb"_cc
-.
-<p>aa_"bb"_cc</p>
-
-This is emphasis, even though the opening delimiter is
-both left- and right-flanking, because it is preceded by
-punctuation:
-foo-_(bar)_
-.
-<p>foo-<em>(bar)</em></p>
-
-Rule 3:
-This is not emphasis, because the closing delimiter does
-not match the opening delimiter:
-_foo*
-.
-<p>_foo*</p>
-
-This is not emphasis, because the closing * is preceded by
-whitespace:
-*foo bar *
-.
-<p>*foo bar *</p>
-
-A newline also counts as whitespace:
-*foo bar
-*
-.
-<p>*foo bar
-*</p>
-
-This is not emphasis, because the second * is
-preceded by punctuation and followed by an alphanumeric
-(hence it is not part of a [right-flanking delimiter run]:
-*(*foo)
-.
-<p>*(*foo)</p>
-
-The point of this restriction is more easily appreciated
-with this example:
-*(*foo*)*
-.
-<p><em>(<em>foo</em>)</em></p>
-
-Intraword emphasis with * is allowed:
-*foo*bar
-.
-<p><em>foo</em>bar</p>
-
-Rule 4:
-This is not emphasis, because the closing _ is preceded by
-whitespace:
-_foo bar _
-.
-<p>_foo bar _</p>
-
-This is not emphasis, because the second _ is
-preceded by punctuation and followed by an alphanumeric:
-_(_foo)
-.
-<p>_(_foo)</p>
-
-This is emphasis within emphasis:
-_(_foo_)_
-.
-<p><em>(<em>foo</em>)</em></p>
-
-Intraword emphasis is disallowed for _:
-_foo_bar
-.
-<p>_foo_bar</p>
-
-_пристаням_стремятся
-.
-<p>_пристаням_стремятся</p>
-
-_foo_bar_baz_
-.
-<p><em>foo_bar_baz</em></p>
-
-This is emphasis, even though the closing delimiter is
-both left- and right-flanking, because it is followed by
-punctuation:
-_(bar)_.
-.
-<p><em>(bar)</em>.</p>
-
-Rule 5:
-**foo bar**
-.
-<p><strong>foo bar</strong></p>
-
-This is not strong emphasis, because the opening delimiter is
-followed by whitespace:
-** foo bar**
-.
-<p>** foo bar**</p>
-
-This is not strong emphasis, because the opening ** is preceded
-by an alphanumeric and followed by punctuation, and hence
-not part of a [left-flanking delimiter run]:
-a**"foo"**
-.
-<p>a**"foo"**</p>
-
-Intraword strong emphasis with ** is permitted:
-foo**bar**
-.
-<p>foo<strong>bar</strong></p>
-
-Rule 6:
-__foo bar__
-.
-<p><strong>foo bar</strong></p>
-
-This is not strong emphasis, because the opening delimiter is
-followed by whitespace:
-__ foo bar__
-.
-<p>__ foo bar__</p>
-
-A newline counts as whitespace:
-__
-foo bar__
-.
-<p>__
-foo bar__</p>
-
-This is not strong emphasis, because the opening __ is preceded
-by an alphanumeric and followed by punctuation:
-a__"foo"__
-.
-<p>a__"foo"__</p>
-
-Intraword strong emphasis is forbidden with __:
-foo__bar__
-.
-<p>foo__bar__</p>
-
-5__6__78
-.
-<p>5__6__78</p>
-
-пристаням__стремятся__
-.
-<p>пристаням__стремятся__</p>
-
-__foo, __bar__, baz__
-.
-<p><strong>foo, <strong>bar</strong>, baz</strong></p>
-
-This is strong emphasis, even though the opening delimiter is
-both left- and right-flanking, because it is preceded by
-punctuation:
-foo-__(bar)__
-.
-<p>foo-<strong>(bar)</strong></p>
-
-Rule 7:
-This is not strong emphasis, because the closing delimiter is preceded
-by whitespace:
-**foo bar **
-.
-<p>**foo bar **</p>
-
-(Nor can it be interpreted as an emphasized *foo bar *, because of
-Rule 11.)
-This is not strong emphasis, because the second ** is
-preceded by punctuation and followed by an alphanumeric:
-**(**foo)
-.
-<p>**(**foo)</p>
-
-The point of this restriction is more easily appreciated
-with these examples:
-*(**foo**)*
-.
-<p><em>(<strong>foo</strong>)</em></p>
-
-**Gomphocarpus (*Gomphocarpus physocarpus*, syn.
-*Asclepias physocarpa*)**
-.
-<p><strong>Gomphocarpus (<em>Gomphocarpus physocarpus</em>, syn.
-<em>Asclepias physocarpa</em>)</strong></p>
-
-**foo "*bar*" foo**
-.
-<p><strong>foo "<em>bar</em>" foo</strong></p>
-
-Intraword emphasis:
-**foo**bar
-.
-<p><strong>foo</strong>bar</p>
-
-Rule 8:
-This is not strong emphasis, because the closing delimiter is
-preceded by whitespace:
-__foo bar __
-.
-<p>__foo bar __</p>
-
-This is not strong emphasis, because the second __ is
-preceded by punctuation and followed by an alphanumeric:
-__(__foo)
-.
-<p>__(__foo)</p>
-
-The point of this restriction is more easily appreciated
-with this example:
-_(__foo__)_
-.
-<p><em>(<strong>foo</strong>)</em></p>
-
-Intraword strong emphasis is forbidden with __:
-__foo__bar
-.
-<p>__foo__bar</p>
-
-__пристаням__стремятся
-.
-<p>__пристаням__стремятся</p>
-
-__foo__bar__baz__
-.
-<p><strong>foo__bar__baz</strong></p>
-
-This is strong emphasis, even though the closing delimiter is
-both left- and right-flanking, because it is followed by
-punctuation:
-__(bar)__.
-.
-<p><strong>(bar)</strong>.</p>
-
-Rule 9:
-Any nonempty sequence of inline elements can be the contents of an
-emphasized span.
-*foo [bar](/url)*
-.
-<p><em>foo <a href="/url">bar</a></em></p>
-
-*foo
-bar*
-.
-<p><em>foo
-bar</em></p>
-
-In particular, emphasis and strong emphasis can be nested
-inside emphasis:
-_foo __bar__ baz_
-.
-<p><em>foo <strong>bar</strong> baz</em></p>
-
-_foo _bar_ baz_
-.
-<p><em>foo <em>bar</em> baz</em></p>
-
-__foo_ bar_
-.
-<p><em><em>foo</em> bar</em></p>
-
-*foo *bar**
-.
-<p><em>foo <em>bar</em></em></p>
-
-*foo **bar** baz*
-.
-<p><em>foo <strong>bar</strong> baz</em></p>
-
-*foo**bar**baz*
-.
-<p><em>foo<strong>bar</strong>baz</em></p>
-
-Note that in the preceding case, the interpretation
-<p><em>foo</em><em>bar<em></em>baz</em></p>
-
-is precluded by the condition that a delimiter that
-can both open and close (like the * after foo)
-cannot form emphasis if the sum of the lengths of
-the delimiter runs containing the opening and
-closing delimiters is a multiple of 3 unless
-both lengths are multiples of 3.
-For the same reason, we don't get two consecutive
-emphasis sections in this example:
-*foo**bar*
-.
-<p><em>foo**bar</em></p>
-
-The same condition ensures that the following
-cases are all strong emphasis nested inside
-emphasis, even when the interior spaces are
-omitted:
-***foo** bar*
-.
-<p><em><strong>foo</strong> bar</em></p>
-
-*foo **bar***
-.
-<p><em>foo <strong>bar</strong></em></p>
-
-*foo**bar***
-.
-<p><em>foo<strong>bar</strong></em></p>
-
-When the lengths of the interior closing and opening
-delimiter runs are both multiples of 3, though,
-they can match to create emphasis:
-foo***bar***baz
-.
-<p>foo<em><strong>bar</strong></em>baz</p>
-
-foo******bar*********baz
-.
-<p>foo<strong><strong><strong>bar</strong></strong></strong>***baz</p>
-
-Indefinite levels of nesting are possible:
-*foo **bar *baz* bim** bop*
-.
-<p><em>foo <strong>bar <em>baz</em> bim</strong> bop</em></p>
-
-*foo [*bar*](/url)*
-.
-<p><em>foo <a href="/url"><em>bar</em></a></em></p>
-
-There can be no empty emphasis or strong emphasis:
-** is not an empty emphasis
-.
-<p>** is not an empty emphasis</p>
-
-**** is not an empty strong emphasis
-.
-<p>**** is not an empty strong emphasis</p>
-
-Rule 10:
-Any nonempty sequence of inline elements can be the contents of an
-strongly emphasized span.
-**foo [bar](/url)**
-.
-<p><strong>foo <a href="/url">bar</a></strong></p>
-
-**foo
-bar**
-.
-<p><strong>foo
-bar</strong></p>
-
-In particular, emphasis and strong emphasis can be nested
-inside strong emphasis:
-__foo _bar_ baz__
-.
-<p><strong>foo <em>bar</em> baz</strong></p>
-
-__foo __bar__ baz__
-.
-<p><strong>foo <strong>bar</strong> baz</strong></p>
-
-____foo__ bar__
-.
-<p><strong><strong>foo</strong> bar</strong></p>
-
-**foo **bar****
-.
-<p><strong>foo <strong>bar</strong></strong></p>
-
-**foo *bar* baz**
-.
-<p><strong>foo <em>bar</em> baz</strong></p>
-
-**foo*bar*baz**
-.
-<p><strong>foo<em>bar</em>baz</strong></p>
-
-***foo* bar**
-.
-<p><strong><em>foo</em> bar</strong></p>
-
-**foo *bar***
-.
-<p><strong>foo <em>bar</em></strong></p>
-
-Indefinite levels of nesting are possible:
-**foo *bar **baz**
-bim* bop**
-.
-<p><strong>foo <em>bar <strong>baz</strong>
-bim</em> bop</strong></p>
-
-**foo [*bar*](/url)**
-.
-<p><strong>foo <a href="/url"><em>bar</em></a></strong></p>
-
-There can be no empty emphasis or strong emphasis:
-__ is not an empty emphasis
-.
-<p>__ is not an empty emphasis</p>
-
-____ is not an empty strong emphasis
-.
-<p>____ is not an empty strong emphasis</p>
-
-Rule 11:
-foo ***
-.
-<p>foo ***</p>
-
-foo *\**
-.
-<p>foo <em>*</em></p>
-
-foo *_*
-.
-<p>foo <em>_</em></p>
-
-foo *****
-.
-<p>foo *****</p>
-
-foo **\***
-.
-<p>foo <strong>*</strong></p>
-
-foo **_**
-.
-<p>foo <strong>_</strong></p>
-
-Note that when delimiters do not match evenly, Rule 11 determines
-that the excess literal * characters will appear outside of the
-emphasis, rather than inside it:
-**foo*
-.
-<p>*<em>foo</em></p>
-
-*foo**
-.
-<p><em>foo</em>*</p>
-
-***foo**
-.
-<p>*<strong>foo</strong></p>
-
-****foo*
-.
-<p>***<em>foo</em></p>
-
-**foo***
-.
-<p><strong>foo</strong>*</p>
-
-*foo****
-.
-<p><em>foo</em>***</p>
-
-Rule 12:
-foo ___
-.
-<p>foo ___</p>
-
-foo _\__
-.
-<p>foo <em>_</em></p>
-
-foo _*_
-.
-<p>foo <em>*</em></p>
-
-foo _____
-.
-<p>foo _____</p>
-
-foo __\___
-.
-<p>foo <strong>_</strong></p>
-
-foo __*__
-.
-<p>foo <strong>*</strong></p>
-
-__foo_
-.
-<p>_<em>foo</em></p>
-
-Note that when delimiters do not match evenly, Rule 12 determines
-that the excess literal _ characters will appear outside of the
-emphasis, rather than inside it:
-_foo__
-.
-<p><em>foo</em>_</p>
-
-___foo__
-.
-<p>_<strong>foo</strong></p>
-
-____foo_
-.
-<p>___<em>foo</em></p>
-
-__foo___
-.
-<p><strong>foo</strong>_</p>
-
-_foo____
-.
-<p><em>foo</em>___</p>
-
-Rule 13 implies that if you want emphasis nested directly inside
-emphasis, you must use different delimiters:
-**foo**
-.
-<p><strong>foo</strong></p>
-
-*_foo_*
-.
-<p><em><em>foo</em></em></p>
-
-__foo__
-.
-<p><strong>foo</strong></p>
-
-_*foo*_
-.
-<p><em><em>foo</em></em></p>
-
-However, strong emphasis within strong emphasis is possible without
-switching delimiters:
-****foo****
-.
-<p><strong><strong>foo</strong></strong></p>
-
-____foo____
-.
-<p><strong><strong>foo</strong></strong></p>
-
-Rule 13 can be applied to arbitrarily long sequences of
-delimiters:
-******foo******
-.
-<p><strong><strong><strong>foo</strong></strong></strong></p>
-
-Rule 14:
-***foo***
-.
-<p><em><strong>foo</strong></em></p>
-
-_____foo_____
-.
-<p><em><strong><strong>foo</strong></strong></em></p>
-
-Rule 15:
-*foo _bar* baz_
-.
-<p><em>foo _bar</em> baz_</p>
-
-*foo __bar *baz bim__ bam*
-.
-<p><em>foo <strong>bar *baz bim</strong> bam</em></p>
-
-Rule 16:
-**foo **bar baz**
-.
-<p>**foo <strong>bar baz</strong></p>
-
-*foo *bar baz*
-.
-<p>*foo <em>bar baz</em></p>
-
-Rule 17:
-*[bar*](/url)
-.
-<p>*<a href="/url">bar*</a></p>
-
-_foo [bar_](/url)
-.
-<p>_foo <a href="/url">bar_</a></p>
-
-*<img src="foo" title="*"/>
-.
-<p>*<img src="foo" title="*"/></p>
-
-**<a href="**">
-.
-<p>**<a href="**"></p>
-
-__<a href="__">
-.
-<p>__<a href="__"></p>
-
-*a `*`*
-.
-<p><em>a <code>*</code></em></p>
-
-_a `_`_
-.
-<p><em>a <code>_</code></em></p>
-
-**a<http://foo.bar/?q=**>
-.
-<p>**a<a href="http://foo.bar/?q=**">http://foo.bar/?q=**</a></p>
-
-__a<http://foo.bar/?q=__>
-.
-<p>__a<a href="http://foo.bar/?q=__">http://foo.bar/?q=__</a></p>
-
-Links
-A link contains [link text] (the visible text), a [link destination]
-(the URI that is the link destination), and optionally a [link title].
-There are two basic kinds of links in Markdown. In [inline links] the
-destination and title are given immediately after the link text. In
-[reference links] the destination and title are defined elsewhere in
-the document.
-A link text consists of a sequence of zero or more
-inline elements enclosed by square brackets ([ and ]). The
-following rules apply:
-
--
-
Links may not contain other links, at any level of nesting. If
-multiple otherwise valid link definitions appear nested inside each
-other, the inner-most definition is used.
-
--
-
Brackets are allowed in the [link text] only if (a) they
-are backslash-escaped or (b) they appear as a matched pair of brackets,
-with an open bracket [, a sequence of zero or more inlines, and
-a close bracket ].
-
--
-
Backtick [code spans], [autolinks], and raw [HTML tags] bind more tightly
-than the brackets in link text. Thus, for example,
-[foo`]` could not be a link text, since the second ]
-is part of a code span.
-
--
-
The brackets in link text bind more tightly than markers for
-[emphasis and strong emphasis]. Thus, for example, *[foo*](url) is a link.
-
-
-A link destination consists of either
-
--
-
a sequence of zero or more characters between an opening < and a
-closing > that contains no line breaks or unescaped
-< or > characters, or
-
--
-
a nonempty sequence of characters that does not start with
-<, does not include ASCII space or control characters, and
-includes parentheses only if (a) they are backslash-escaped or
-(b) they are part of a balanced pair of unescaped parentheses.
-(Implementations may impose limits on parentheses nesting to
-avoid performance issues, but at least three levels of nesting
-should be supported.)
-
-
-A link title consists of either
-
--
-
a sequence of zero or more characters between straight double-quote
-characters ("), including a " character only if it is
-backslash-escaped, or
-
--
-
a sequence of zero or more characters between straight single-quote
-characters ('), including a ' character only if it is
-backslash-escaped, or
-
--
-
a sequence of zero or more characters between matching parentheses
-((...)), including a ( or ) character only if it is
-backslash-escaped.
-
-
-Although [link titles] may span multiple lines, they may not contain
-a [blank line].
-An inline link consists of a [link text] followed immediately
-by a left parenthesis (, optional [whitespace], an optional
-[link destination], an optional [link title] separated from the link
-destination by [whitespace], optional [whitespace], and a right
-parenthesis ). The link's text consists of the inlines contained
-in the [link text] (excluding the enclosing square brackets).
-The link's URI consists of the link destination, excluding enclosing
-<...> if present, with backslash-escapes in effect as described
-above. The link's title consists of the link title, excluding its
-enclosing delimiters, with backslash-escapes in effect as described
-above.
-Here is a simple inline link:
-[link](/uri "title")
-.
-<p><a href="/uri" title="title">link</a></p>
-
-The title may be omitted:
-[link](/uri)
-.
-<p><a href="/uri">link</a></p>
-
-Both the title and the destination may be omitted:
-[link]()
-.
-<p><a href="">link</a></p>
-
-[link](<>)
-.
-<p><a href="">link</a></p>
-
-The destination can only contain spaces if it is
-enclosed in pointy brackets:
-[link](/my uri)
-.
-<p>[link](/my uri)</p>
-
-[link](</my uri>)
-.
-<p><a href="/my%20uri">link</a></p>
-
-The destination cannot contain line breaks,
-even if enclosed in pointy brackets:
-[link](foo
-bar)
-.
-<p>[link](foo
-bar)</p>
-
-[link](<foo
-bar>)
-.
-<p>[link](<foo
-bar>)</p>
-
-The destination can contain ) if it is enclosed
-in pointy brackets:
-[a](<b)c>)
-.
-<p><a href="b)c">a</a></p>
-
-Pointy brackets that enclose links must be unescaped:
-[link](<foo\>)
-.
-<p>[link](<foo>)</p>
-
-These are not links, because the opening pointy bracket
-is not matched properly:
-[a](<b)c
-[a](<b)c>
-[a](<b>c)
-.
-<p>[a](<b)c
-[a](<b)c>
-[a](<b>c)</p>
-
-Parentheses inside the link destination may be escaped:
-[link](\(foo\))
-.
-<p><a href="(foo)">link</a></p>
-
-Any number of parentheses are allowed without escaping, as long as they are
-balanced:
-[link](foo(and(bar)))
-.
-<p><a href="foo(and(bar))">link</a></p>
-
-However, if you have unbalanced parentheses, you need to escape or use the
-<...> form:
-[link](foo\(and\(bar\))
-.
-<p><a href="foo(and(bar)">link</a></p>
-
-[link](<foo(and(bar)>)
-.
-<p><a href="foo(and(bar)">link</a></p>
-
-Parentheses and other symbols can also be escaped, as usual
-in Markdown:
-[link](foo\)\:)
-.
-<p><a href="foo):">link</a></p>
-
-A link can contain fragment identifiers and queries:
-[link](#fragment)
-
-[link](http://example.com#fragment)
-
-[link](http://example.com?foo=3#frag)
-.
-<p><a href="#fragment">link</a></p>
-<p><a href="http://example.com#fragment">link</a></p>
-<p><a href="http://example.com?foo=3#frag">link</a></p>
-
-Note that a backslash before a non-escapable character is
-just a backslash:
-[link](foo\bar)
-.
-<p><a href="foo%5Cbar">link</a></p>
-
-URL-escaping should be left alone inside the destination, as all
-URL-escaped characters are also valid URL characters. Entity and
-numerical character references in the destination will be parsed
-into the corresponding Unicode code points, as usual. These may
-be optionally URL-escaped when written as HTML, but this spec
-does not enforce any particular policy for rendering URLs in
-HTML or other formats. Renderers may make different decisions
-about how to escape or normalize URLs in the output.
-[link](foo%20bä)
-.
-<p><a href="foo%20b%C3%A4">link</a></p>
-
-Note that, because titles can often be parsed as destinations,
-if you try to omit the destination and keep the title, you'll
-get unexpected results:
-[link]("title")
-.
-<p><a href="%22title%22">link</a></p>
-
-Titles may be in single quotes, double quotes, or parentheses:
-[link](/url "title")
-[link](/url 'title')
-[link](/url (title))
-.
-<p><a href="/url" title="title">link</a>
-<a href="/url" title="title">link</a>
-<a href="/url" title="title">link</a></p>
-
-Backslash escapes and entity and numeric character references
-may be used in titles:
-[link](/url "title \""")
-.
-<p><a href="/url" title="title """>link</a></p>
-
-Titles must be separated from the link using a [whitespace].
-Other [Unicode whitespace] like non-breaking space doesn't work.
-[link](/url "title")
-.
-<p><a href="/url%C2%A0%22title%22">link</a></p>
-
-Nested balanced quotes are not allowed without escaping:
-[link](/url "title "and" title")
-.
-<p>[link](/url "title "and" title")</p>
-
-But it is easy to work around this by using a different quote type:
-[link](/url 'title "and" title')
-.
-<p><a href="/url" title="title "and" title">link</a></p>
-
-(Note: Markdown.pl did allow double quotes inside a double-quoted
-title, and its test suite included a test demonstrating this.
-But it is hard to see a good rationale for the extra complexity this
-brings, since there are already many ways---backslash escaping,
-entity and numeric character references, or using a different
-quote type for the enclosing title---to write titles containing
-double quotes. Markdown.pl's handling of titles has a number
-of other strange features. For example, it allows single-quoted
-titles in inline links, but not reference links. And, in
-reference links but not inline links, it allows a title to begin
-with " and end with ). Markdown.pl 1.0.1 even allows
-titles with no closing quotation mark, though 1.0.2b8 does not.
-It seems preferable to adopt a simple, rational rule that works
-the same way in inline links and link reference definitions.)
-[Whitespace] is allowed around the destination and title:
-[link]( /uri
- "title" )
-.
-<p><a href="/uri" title="title">link</a></p>
-
-But it is not allowed between the link text and the
-following parenthesis:
-[link] (/uri)
-.
-<p>[link] (/uri)</p>
-
-The link text may contain balanced brackets, but not unbalanced ones,
-unless they are escaped:
-[link [foo [bar]]](/uri)
-.
-<p><a href="/uri">link [foo [bar]]</a></p>
-
-[link] bar](/uri)
-.
-<p>[link] bar](/uri)</p>
-
-[link [bar](/uri)
-.
-<p>[link <a href="/uri">bar</a></p>
-
-[link \[bar](/uri)
-.
-<p><a href="/uri">link [bar</a></p>
-
-The link text may contain inline content:
-[link *foo **bar** `#`*](/uri)
-.
-<p><a href="/uri">link <em>foo <strong>bar</strong> <code>#</code></em></a></p>
-
-[](/uri)
-.
-<p><a href="/uri"><img src="moon.jpg" alt="moon" /></a></p>
-
-However, links may not contain other links, at any level of nesting.
-[foo [bar](/uri)](/uri)
-.
-<p>[foo <a href="/uri">bar</a>](/uri)</p>
-
-[foo *[bar [baz](/uri)](/uri)*](/uri)
-.
-<p>[foo <em>[bar <a href="/uri">baz</a>](/uri)</em>](/uri)</p>
-
-](uri2)](uri3)
-.
-<p><img src="uri3" alt="[foo](uri2)" /></p>
-
-These cases illustrate the precedence of link text grouping over
-emphasis grouping:
-*[foo*](/uri)
-.
-<p>*<a href="/uri">foo*</a></p>
-
-[foo *bar](baz*)
-.
-<p><a href="baz*">foo *bar</a></p>
-
-Note that brackets that aren't part of links do not take
-precedence:
-*foo [bar* baz]
-.
-<p><em>foo [bar</em> baz]</p>
-
-These cases illustrate the precedence of HTML tags, code spans,
-and autolinks over link grouping:
-[foo <bar attr="](baz)">
-.
-<p>[foo <bar attr="](baz)"></p>
-
-[foo`](/uri)`
-.
-<p>[foo<code>](/uri)</code></p>
-
-[foo<http://example.com/?search=](uri)>
-.
-<p>[foo<a href="http://example.com/?search=%5D(uri)">http://example.com/?search=](uri)</a></p>
-
-There are three kinds of reference links:
-full, collapsed,
-and shortcut.
-A full reference link
-consists of a [link text] immediately followed by a [link label]
-that [matches] a [link reference definition] elsewhere in the document.
-A link label begins with a left bracket ([) and ends
-with the first right bracket (]) that is not backslash-escaped.
-Between these brackets there must be at least one [non-whitespace character].
-Unescaped square bracket characters are not allowed inside the
-opening and closing square brackets of [link labels]. A link
-label can have at most 999 characters inside the square
-brackets.
-One label matches
-another just in case their normalized forms are equal. To normalize a
-label, strip off the opening and closing brackets,
-perform the Unicode case fold, strip leading and trailing
-[whitespace] and collapse consecutive internal
-[whitespace] to a single space. If there are multiple
-matching reference link definitions, the one that comes first in the
-document is used. (It is desirable in such cases to emit a warning.)
-The contents of the first link label are parsed as inlines, which are
-used as the link's text. The link's URI and title are provided by the
-matching [link reference definition].
-Here is a simple example:
-[foo][bar]
-
-[bar]: /url "title"
-.
-<p><a href="/url" title="title">foo</a></p>
-
-The rules for the [link text] are the same as with
-[inline links]. Thus:
-The link text may contain balanced brackets, but not unbalanced ones,
-unless they are escaped:
-[link [foo [bar]]][ref]
-
-[ref]: /uri
-.
-<p><a href="/uri">link [foo [bar]]</a></p>
-
-[link \[bar][ref]
-
-[ref]: /uri
-.
-<p><a href="/uri">link [bar</a></p>
-
-The link text may contain inline content:
-[link *foo **bar** `#`*][ref]
-
-[ref]: /uri
-.
-<p><a href="/uri">link <em>foo <strong>bar</strong> <code>#</code></em></a></p>
-
-[][ref]
-
-[ref]: /uri
-.
-<p><a href="/uri"><img src="moon.jpg" alt="moon" /></a></p>
-
-However, links may not contain other links, at any level of nesting.
-[foo [bar](/uri)][ref]
-
-[ref]: /uri
-.
-<p>[foo <a href="/uri">bar</a>]<a href="/uri">ref</a></p>
-
-[foo *bar [baz][ref]*][ref]
-
-[ref]: /uri
-.
-<p>[foo <em>bar <a href="/uri">baz</a></em>]<a href="/uri">ref</a></p>
-
-(In the examples above, we have two [shortcut reference links]
-instead of one [full reference link].)
-The following cases illustrate the precedence of link text grouping over
-emphasis grouping:
-*[foo*][ref]
-
-[ref]: /uri
-.
-<p>*<a href="/uri">foo*</a></p>
-
-[foo *bar][ref]
-
-[ref]: /uri
-.
-<p><a href="/uri">foo *bar</a></p>
-
-These cases illustrate the precedence of HTML tags, code spans,
-and autolinks over link grouping:
-[foo <bar attr="][ref]">
-
-[ref]: /uri
-.
-<p>[foo <bar attr="][ref]"></p>
-
-[foo`][ref]`
-
-[ref]: /uri
-.
-<p>[foo<code>][ref]</code></p>
-
-[foo<http://example.com/?search=][ref]>
-
-[ref]: /uri
-.
-<p>[foo<a href="http://example.com/?search=%5D%5Bref%5D">http://example.com/?search=][ref]</a></p>
-
-Matching is case-insensitive:
-[foo][BaR]
-
-[bar]: /url "title"
-.
-<p><a href="/url" title="title">foo</a></p>
-
-Unicode case fold is used:
-[Толпой][Толпой] is a Russian word.
-
-[ТОЛПОЙ]: /url
-.
-<p><a href="/url">Толпой</a> is a Russian word.</p>
-
-Consecutive internal [whitespace] is treated as one space for
-purposes of determining matching:
-[Foo
- bar]: /url
-
-[Baz][Foo bar]
-.
-<p><a href="/url">Baz</a></p>
-
-No [whitespace] is allowed between the [link text] and the
-[link label]:
-[foo] [bar]
-
-[bar]: /url "title"
-.
-<p>[foo] <a href="/url" title="title">bar</a></p>
-
-[foo]
-[bar]
-
-[bar]: /url "title"
-.
-<p>[foo]
-<a href="/url" title="title">bar</a></p>
-
-This is a departure from John Gruber's original Markdown syntax
-description, which explicitly allows whitespace between the link
-text and the link label. It brings reference links in line with
-[inline links], which (according to both original Markdown and
-this spec) cannot have whitespace after the link text. More
-importantly, it prevents inadvertent capture of consecutive
-[shortcut reference links]. If whitespace is allowed between the
-link text and the link label, then in the following we will have
-a single reference link, not two shortcut reference links, as
-intended:
-[foo]
-[bar]
-
-[foo]: /url1
-[bar]: /url2
-
-(Note that [shortcut reference links] were introduced by Gruber
-himself in a beta version of Markdown.pl, but never included
-in the official syntax description. Without shortcut reference
-links, it is harmless to allow space between the link text and
-link label; but once shortcut references are introduced, it is
-too dangerous to allow this, as it frequently leads to
-unintended results.)
-When there are multiple matching [link reference definitions],
-the first is used:
-[foo]: /url1
-
-[foo]: /url2
-
-[bar][foo]
-.
-<p><a href="/url1">bar</a></p>
-
-Note that matching is performed on normalized strings, not parsed
-inline content. So the following does not match, even though the
-labels define equivalent inline content:
-[bar][foo\!]
-
-[foo!]: /url
-.
-<p>[bar][foo!]</p>
-
-[Link labels] cannot contain brackets, unless they are
-backslash-escaped:
-[foo][ref[]
-
-[ref[]: /uri
-.
-<p>[foo][ref[]</p>
-<p>[ref[]: /uri</p>
-
-[foo][ref[bar]]
-
-[ref[bar]]: /uri
-.
-<p>[foo][ref[bar]]</p>
-<p>[ref[bar]]: /uri</p>
-
-[[[foo]]]
-
-[[[foo]]]: /url
-.
-<p>[[[foo]]]</p>
-<p>[[[foo]]]: /url</p>
-
-[foo][ref\[]
-
-[ref\[]: /uri
-.
-<p><a href="/uri">foo</a></p>
-
-Note that in this example ] is not backslash-escaped:
-[bar\\]: /uri
-
-[bar\\]
-.
-<p><a href="/uri">bar\</a></p>
-
-A [link label] must contain at least one [non-whitespace character]:
-[]
-
-[]: /uri
-.
-<p>[]</p>
-<p>[]: /uri</p>
-
-[
- ]
-
-[
- ]: /uri
-.
-<p>[
-]</p>
-<p>[
-]: /uri</p>
-
-A collapsed reference link
-consists of a [link label] that [matches] a
-[link reference definition] elsewhere in the
-document, followed by the string [].
-The contents of the first link label are parsed as inlines,
-which are used as the link's text. The link's URI and title are
-provided by the matching reference link definition. Thus,
-[foo][] is equivalent to [foo][foo].
-[foo][]
-
-[foo]: /url "title"
-.
-<p><a href="/url" title="title">foo</a></p>
-
-[*foo* bar][]
-
-[*foo* bar]: /url "title"
-.
-<p><a href="/url" title="title"><em>foo</em> bar</a></p>
-
-The link labels are case-insensitive:
-[Foo][]
-
-[foo]: /url "title"
-.
-<p><a href="/url" title="title">Foo</a></p>
-
-As with full reference links, [whitespace] is not
-allowed between the two sets of brackets:
-[foo]
-[]
-
-[foo]: /url "title"
-.
-<p><a href="/url" title="title">foo</a>
-[]</p>
-
-A shortcut reference link
-consists of a [link label] that [matches] a
-[link reference definition] elsewhere in the
-document and is not followed by [] or a link label.
-The contents of the first link label are parsed as inlines,
-which are used as the link's text. The link's URI and title
-are provided by the matching link reference definition.
-Thus, [foo] is equivalent to [foo][].
-[foo]
-
-[foo]: /url "title"
-.
-<p><a href="/url" title="title">foo</a></p>
-
-[*foo* bar]
-
-[*foo* bar]: /url "title"
-.
-<p><a href="/url" title="title"><em>foo</em> bar</a></p>
-
-[[*foo* bar]]
-
-[*foo* bar]: /url "title"
-.
-<p>[<a href="/url" title="title"><em>foo</em> bar</a>]</p>
-
-[[bar [foo]
-
-[foo]: /url
-.
-<p>[[bar <a href="/url">foo</a></p>
-
-The link labels are case-insensitive:
-[Foo]
-
-[foo]: /url "title"
-.
-<p><a href="/url" title="title">Foo</a></p>
-
-A space after the link text should be preserved:
-[foo] bar
-
-[foo]: /url
-.
-<p><a href="/url">foo</a> bar</p>
-
-If you just want bracketed text, you can backslash-escape the
-opening bracket to avoid links:
-\[foo]
-
-[foo]: /url "title"
-.
-<p>[foo]</p>
-
-Note that this is a link, because a link label ends with the first
-following closing bracket:
-[foo*]: /url
-
-*[foo*]
-.
-<p>*<a href="/url">foo*</a></p>
-
-Full and compact references take precedence over shortcut
-references:
-[foo][bar]
-
-[foo]: /url1
-[bar]: /url2
-.
-<p><a href="/url2">foo</a></p>
-
-[foo][]
-
-[foo]: /url1
-.
-<p><a href="/url1">foo</a></p>
-
-Inline links also take precedence:
-[foo]()
-
-[foo]: /url1
-.
-<p><a href="">foo</a></p>
-
-[foo](not a link)
-
-[foo]: /url1
-.
-<p><a href="/url1">foo</a>(not a link)</p>
-
-In the following case [bar][baz] is parsed as a reference,
-[foo] as normal text:
-[foo][bar][baz]
-
-[baz]: /url
-.
-<p>[foo]<a href="/url">bar</a></p>
-
-Here, though, [foo][bar] is parsed as a reference, since
-[bar] is defined:
-[foo][bar][baz]
-
-[baz]: /url1
-[bar]: /url2
-.
-<p><a href="/url2">foo</a><a href="/url1">baz</a></p>
-
-Here [foo] is not parsed as a shortcut reference, because it
-is followed by a link label (even though [bar] is not defined):
-[foo][bar][baz]
-
-[baz]: /url1
-[foo]: /url2
-.
-<p>[foo]<a href="/url1">bar</a></p>
-
-Images
-Syntax for images is like the syntax for links, with one
-difference. Instead of [link text], we have an
-image description. The rules for this are the
-same as for [link text], except that (a) an
-image description starts with 
-.
-<p><img src="/url" alt="foo" title="title" /></p>
-
-![foo *bar*]
-
-[foo *bar*]: train.jpg "train & tracks"
-.
-<p><img src="train.jpg" alt="foo bar" title="train & tracks" /></p>
-
-](/url2)
-.
-<p><img src="/url2" alt="foo bar" /></p>
-
-](/url2)
-.
-<p><img src="/url2" alt="foo bar" /></p>
-
-Though this spec is concerned with parsing, not rendering, it is
-recommended that in rendering to HTML, only the plain string content
-of the [image description] be used. Note that in
-the above example, the alt attribute's value is foo bar, not foo [bar](/url) or foo <a href="/url">bar</a>. Only the plain string
-content is rendered, without formatting.
-![foo *bar*][]
-
-[foo *bar*]: train.jpg "train & tracks"
-.
-<p><img src="train.jpg" alt="foo bar" title="train & tracks" /></p>
-
-![foo *bar*][foobar]
-
-[FOOBAR]: train.jpg "train & tracks"
-.
-<p><img src="train.jpg" alt="foo bar" title="train & tracks" /></p>
-
-
-.
-<p><img src="train.jpg" alt="foo" /></p>
-
-My 
-.
-<p>My <img src="/path/to/train.jpg" alt="foo bar" title="title" /></p>
-
-
-.
-<p><img src="url" alt="foo" /></p>
-
-
-.
-<p><img src="/url" alt="" /></p>
-
-Reference-style:
-![foo][bar]
-
-[bar]: /url
-.
-<p><img src="/url" alt="foo" /></p>
-
-![foo][bar]
-
-[BAR]: /url
-.
-<p><img src="/url" alt="foo" /></p>
-
-Collapsed:
-![foo][]
-
-[foo]: /url "title"
-.
-<p><img src="/url" alt="foo" title="title" /></p>
-
-![*foo* bar][]
-
-[*foo* bar]: /url "title"
-.
-<p><img src="/url" alt="foo bar" title="title" /></p>
-
-The labels are case-insensitive:
-![Foo][]
-
-[foo]: /url "title"
-.
-<p><img src="/url" alt="Foo" title="title" /></p>
-
-As with reference links, [whitespace] is not allowed
-between the two sets of brackets:
-![foo]
-[]
-
-[foo]: /url "title"
-.
-<p><img src="/url" alt="foo" title="title" />
-[]</p>
-
-Shortcut:
-![foo]
-
-[foo]: /url "title"
-.
-<p><img src="/url" alt="foo" title="title" /></p>
-
-![*foo* bar]
-
-[*foo* bar]: /url "title"
-.
-<p><img src="/url" alt="foo bar" title="title" /></p>
-
-Note that link labels cannot contain unescaped brackets:
-![[foo]]
-
-[[foo]]: /url "title"
-.
-<p>![[foo]]</p>
-<p>[[foo]]: /url "title"</p>
-
-The link labels are case-insensitive:
-![Foo]
-
-[foo]: /url "title"
-.
-<p><img src="/url" alt="Foo" title="title" /></p>
-
-If you just want a literal ! followed by bracketed text, you can
-backslash-escape the opening [:
-!\[foo]
-
-[foo]: /url "title"
-.
-<p>![foo]</p>
-
-If you want a link after a literal !, backslash-escape the
-!:
-\![foo]
-
-[foo]: /url "title"
-.
-<p>!<a href="/url" title="title">foo</a></p>
-
-Autolinks
-Autolinks are absolute URIs and email addresses inside
-< and >. They are parsed as links, with the URL or email address
-as the link label.
-A URI autolink consists of <, followed by an
-[absolute URI] followed by >. It is parsed as
-a link to the URI, with the URI as the link's label.
-An absolute URI,
-for these purposes, consists of a [scheme] followed by a colon (:)
-followed by zero or more characters other than ASCII
-[whitespace] and control characters, <, and >. If
-the URI includes these characters, they must be percent-encoded
-(e.g. %20 for a space).
-For purposes of this spec, a scheme is any sequence
-of 2--32 characters beginning with an ASCII letter and followed
-by any combination of ASCII letters, digits, or the symbols plus
-("+"), period ("."), or hyphen ("-").
-Here are some valid autolinks:
-<http://foo.bar.baz>
-.
-<p><a href="http://foo.bar.baz">http://foo.bar.baz</a></p>
-
-<http://foo.bar.baz/test?q=hello&id=22&boolean>
-.
-<p><a href="http://foo.bar.baz/test?q=hello&id=22&boolean">http://foo.bar.baz/test?q=hello&id=22&boolean</a></p>
-
-<irc://foo.bar:2233/baz>
-.
-<p><a href="irc://foo.bar:2233/baz">irc://foo.bar:2233/baz</a></p>
-
-Uppercase is also fine:
-<MAILTO:FOO@BAR.BAZ>
-.
-<p><a href="MAILTO:FOO@BAR.BAZ">MAILTO:FOO@BAR.BAZ</a></p>
-
-Note that many strings that count as [absolute URIs] for
-purposes of this spec are not valid URIs, because their
-schemes are not registered or because of other problems
-with their syntax:
-<a+b+c:d>
-.
-<p><a href="a+b+c:d">a+b+c:d</a></p>
-
-<made-up-scheme://foo,bar>
-.
-<p><a href="made-up-scheme://foo,bar">made-up-scheme://foo,bar</a></p>
-
-<http://../>
-.
-<p><a href="http://../">http://../</a></p>
-
-<localhost:5001/foo>
-.
-<p><a href="localhost:5001/foo">localhost:5001/foo</a></p>
-
-Spaces are not allowed in autolinks:
-<http://foo.bar/baz bim>
-.
-<p><http://foo.bar/baz bim></p>
-
-Backslash-escapes do not work inside autolinks:
-<http://example.com/\[\>
-.
-<p><a href="http://example.com/%5C%5B%5C">http://example.com/\[\</a></p>
-
-An email autolink
-consists of <, followed by an [email address],
-followed by >. The link's label is the email address,
-and the URL is mailto: followed by the email address.
-An email address,
-for these purposes, is anything that matches
-the non-normative regex from the HTML5
-spec:
-/^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?
-(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/
-
-Examples of email autolinks:
-<foo@bar.example.com>
-.
-<p><a href="mailto:foo@bar.example.com">foo@bar.example.com</a></p>
-
-<foo+special@Bar.baz-bar0.com>
-.
-<p><a href="mailto:foo+special@Bar.baz-bar0.com">foo+special@Bar.baz-bar0.com</a></p>
-
-Backslash-escapes do not work inside email autolinks:
-<foo\+@bar.example.com>
-.
-<p><foo+@bar.example.com></p>
-
-These are not autolinks:
-<>
-.
-<p><></p>
-
-< http://foo.bar >
-.
-<p>< http://foo.bar ></p>
-
-<m:abc>
-.
-<p><m:abc></p>
-
-<foo.bar.baz>
-.
-<p><foo.bar.baz></p>
-
-http://example.com
-.
-<p>http://example.com</p>
-
-foo@bar.example.com
-.
-<p>foo@bar.example.com</p>
-
-Raw HTML
-Text between < and > that looks like an HTML tag is parsed as a
-raw HTML tag and will be rendered in HTML without escaping.
-Tag and attribute names are not limited to current HTML tags,
-so custom tags (and even, say, DocBook tags) may be used.
-Here is the grammar for tags:
-A tag name consists of an ASCII letter
-followed by zero or more ASCII letters, digits, or
-hyphens (-).
-An attribute consists of [whitespace],
-an [attribute name], and an optional
-[attribute value specification].
-An attribute name
-consists of an ASCII letter, _, or :, followed by zero or more ASCII
-letters, digits, _, ., :, or -. (Note: This is the XML
-specification restricted to ASCII. HTML5 is laxer.)
-An attribute value specification
-consists of optional [whitespace],
-a = character, optional [whitespace], and an [attribute
-value].
-An attribute value
-consists of an [unquoted attribute value],
-a [single-quoted attribute value], or a [double-quoted attribute value].
-An unquoted attribute value
-is a nonempty string of characters not
-including [whitespace], ", ', =, <, >, or `.
-A single-quoted attribute value
-consists of ', zero or more
-characters not including ', and a final '.
-A double-quoted attribute value
-consists of ", zero or more
-characters not including ", and a final ".
-An open tag consists of a < character, a [tag name],
-zero or more [attributes], optional [whitespace], an optional /
-character, and a > character.
-A closing tag consists of the string </, a
-[tag name], optional [whitespace], and the character >.
-An HTML comment consists of <!-- + text + -->,
-where text does not start with > or ->, does not end with -,
-and does not contain --. (See the
-HTML5 spec.)
-A processing instruction
-consists of the string <?, a string
-of characters not including the string ?>, and the string
-?>.
-A declaration consists of the
-string <!, a name consisting of one or more uppercase ASCII letters,
-[whitespace], a string of characters not including the
-character >, and the character >.
-A CDATA section consists of
-the string <![CDATA[, a string of characters not including the string
-]]>, and the string ]]>.
-An HTML tag consists of an [open tag], a [closing tag],
-an [HTML comment], a [processing instruction], a [declaration],
-or a [CDATA section].
-Here are some simple open tags:
-<a><bab><c2c>
-.
-<p><a><bab><c2c></p>
-
-Empty elements:
-<a/><b2/>
-.
-<p><a/><b2/></p>
-
-[Whitespace] is allowed:
-<a /><b2
-data="foo" >
-.
-<p><a /><b2
-data="foo" ></p>
-
-With attributes:
-<a foo="bar" bam = 'baz <em>"</em>'
-_boolean zoop:33=zoop:33 />
-.
-<p><a foo="bar" bam = 'baz <em>"</em>'
-_boolean zoop:33=zoop:33 /></p>
-
-Custom tag names can be used:
-Foo <responsive-image src="foo.jpg" />
-.
-<p>Foo <responsive-image src="foo.jpg" /></p>
-
-Illegal tag names, not parsed as HTML:
-<33> <__>
-.
-<p><33> <__></p>
-
-Illegal attribute names:
-<a h*#ref="hi">
-.
-<p><a h*#ref="hi"></p>
-
-Illegal attribute values:
-<a href="hi'> <a href=hi'>
-.
-<p><a href="hi'> <a href=hi'></p>
-
-Illegal [whitespace]:
-< a><
-foo><bar/ >
-<foo bar=baz
-bim!bop />
-.
-<p>< a><
-foo><bar/ >
-<foo bar=baz
-bim!bop /></p>
-
-Missing [whitespace]:
-<a href='http://github.com/bar'title=title>
-.
-<p><a href='http://github.com/bar'title=title></p>
-
-Closing tags:
-</a></foo >
-.
-<p></a></foo ></p>
-
-Illegal attributes in closing tag:
-</a href="foo">
-.
-<p></a href="foo"></p>
-
-Comments:
-foo <!-- this is a
-comment - with hyphen -->
-.
-<p>foo <!-- this is a
-comment - with hyphen --></p>
-
-foo <!-- not a comment -- two hyphens -->
-.
-<p>foo <!-- not a comment -- two hyphens --></p>
-
-Not comments:
-foo <!--> foo -->
-
-foo <!-- foo--->
-.
-<p>foo <!--> foo --></p>
-<p>foo <!-- foo---></p>
-
-Processing instructions:
-foo <?php echo $a; ?>
-.
-<p>foo <?php echo $a; ?></p>
-
-Declarations:
-foo <!ELEMENT br EMPTY>
-.
-<p>foo <!ELEMENT br EMPTY></p>
-
-CDATA sections:
-foo <![CDATA[>&<]]>
-.
-<p>foo <![CDATA[>&<]]></p>
-
-Entity and numeric character references are preserved in HTML
-attributes:
-foo <a href="ö">
-.
-<p>foo <a href="ö"></p>
-
-Backslash escapes do not work in HTML attributes:
-foo <a href="\*">
-.
-<p>foo <a href="\*"></p>
-
-<a href="\"">
-.
-<p><a href="""></p>
-
-Hard line breaks
-A line break (not in a code span or HTML tag) that is preceded
-by two or more spaces and does not occur at the end of a block
-is parsed as a hard line break (rendered
-in HTML as a <br /> tag):
-foo
-baz
-.
-<p>foo<br />
-baz</p>
-
-For a more visible alternative, a backslash before the
-[line ending] may be used instead of two spaces:
-foo\
-baz
-.
-<p>foo<br />
-baz</p>
-
-More than two spaces can be used:
-foo
-baz
-.
-<p>foo<br />
-baz</p>
-
-Leading spaces at the beginning of the next line are ignored:
-foo
- bar
-.
-<p>foo<br />
-bar</p>
-
-foo\
- bar
-.
-<p>foo<br />
-bar</p>
-
-Line breaks can occur inside emphasis, links, and other constructs
-that allow inline content:
-*foo
-bar*
-.
-<p><em>foo<br />
-bar</em></p>
-
-*foo\
-bar*
-.
-<p><em>foo<br />
-bar</em></p>
-
-Line breaks do not occur inside code spans
-`code
-span`
-.
-<p><code>code span</code></p>
-
-`code\
-span`
-.
-<p><code>code\ span</code></p>
-
-or HTML tags:
-<a href="foo
-bar">
-.
-<p><a href="foo
-bar"></p>
-
-<a href="foo\
-bar">
-.
-<p><a href="foo\
-bar"></p>
-
-Hard line breaks are for separating inline content within a block.
-Neither syntax for hard line breaks works at the end of a paragraph or
-other block element:
-foo\
-.
-<p>foo\</p>
-
-foo
-.
-<p>foo</p>
-
-### foo\
-.
-<h3>foo\</h3>
-
-### foo
-.
-<h3>foo</h3>
-
-Soft line breaks
-A regular line break (not in a code span or HTML tag) that is not
-preceded by two or more spaces or a backslash is parsed as a
-softbreak. (A softbreak may be rendered in HTML either as a
-[line ending] or as a space. The result will be the same in
-browsers. In the examples here, a [line ending] will be used.)
-foo
-baz
-.
-<p>foo
-baz</p>
-
-Spaces at the end of the line and beginning of the next line are
-removed:
-foo
- baz
-.
-<p>foo
-baz</p>
-
-A conforming parser may render a soft line break in HTML either as a
-line break or as a space.
-A renderer may also provide an option to render soft line breaks
-as hard line breaks.
-Textual content
-Any characters not given an interpretation by the above rules will
-be parsed as plain textual content.
-hello $.;'there
-.
-<p>hello $.;'there</p>
-
-Foo χρῆν
-.
-<p>Foo χρῆν</p>
-
-Internal spaces are preserved verbatim:
-Multiple spaces
-.
-<p>Multiple spaces</p>
-
-
-Appendix: A parsing strategy
-In this appendix we describe some features of the parsing strategy
-used in the CommonMark reference implementations.
-Overview
-Parsing has two phases:
-
--
-
In the first phase, lines of input are consumed and the block
-structure of the document---its division into paragraphs, block quotes,
-list items, and so on---is constructed. Text is assigned to these
-blocks but not parsed. Link reference definitions are parsed and a
-map of links is constructed.
-
--
-
In the second phase, the raw text contents of paragraphs and headings
-are parsed into sequences of Markdown inline elements (strings,
-code spans, links, emphasis, and so on), using the map of link
-references constructed in phase 1.
-
-
-At each point in processing, the document is represented as a tree of
-blocks. The root of the tree is a document block. The document
-may have any number of other blocks as children. These children
-may, in turn, have other blocks as children. The last child of a block
-is normally considered open, meaning that subsequent lines of input
-can alter its contents. (Blocks that are not open are closed.)
-Here, for example, is a possible document tree, with the open blocks
-marked by arrows:
--> document
- -> block_quote
- paragraph
- "Lorem ipsum dolor\nsit amet."
- -> list (type=bullet tight=true bullet_char=-)
- list_item
- paragraph
- "Qui *quodsi iracundia*"
- -> list_item
- -> paragraph
- "aliquando id"
-
-Phase 1: block structure
-Each line that is processed has an effect on this tree. The line is
-analyzed and, depending on its contents, the document may be altered
-in one or more of the following ways:
-
-- One or more open blocks may be closed.
-- One or more new blocks may be created as children of the
-last open block.
-- Text may be added to the last (deepest) open block remaining
-on the tree.
-
-Once a line has been incorporated into the tree in this way,
-it can be discarded, so input can be read in a stream.
-For each line, we follow this procedure:
-
--
-
First we iterate through the open blocks, starting with the
-root document, and descending through last children down to the last
-open block. Each block imposes a condition that the line must satisfy
-if the block is to remain open. For example, a block quote requires a
-> character. A paragraph requires a non-blank line.
-In this phase we may match all or just some of the open
-blocks. But we cannot close unmatched blocks yet, because we may have a
-[lazy continuation line].
-
--
-
Next, after consuming the continuation markers for existing
-blocks, we look for new block starts (e.g. > for a block quote).
-If we encounter a new block start, we close any blocks unmatched
-in step 1 before creating the new block as a child of the last
-matched block.
-
--
-
Finally, we look at the remainder of the line (after block
-markers like >, list markers, and indentation have been consumed).
-This is text that can be incorporated into the last open
-block (a paragraph, code block, heading, or raw HTML).
-
-
-Setext headings are formed when we see a line of a paragraph
-that is a [setext heading underline].
-Reference link definitions are detected when a paragraph is closed;
-the accumulated text lines are parsed to see if they begin with
-one or more reference link definitions. Any remainder becomes a
-normal paragraph.
-We can see how this works by considering how the tree above is
-generated by four lines of Markdown:
-> Lorem ipsum dolor
-sit amet.
-> - Qui *quodsi iracundia*
-> - aliquando id
-
-At the outset, our document model is just
--> document
-
-The first line of our text,
-> Lorem ipsum dolor
-
-causes a block_quote block to be created as a child of our
-open document block, and a paragraph block as a child of
-the block_quote. Then the text is added to the last open
-block, the paragraph:
--> document
- -> block_quote
- -> paragraph
- "Lorem ipsum dolor"
-
-The next line,
-sit amet.
-
-is a "lazy continuation" of the open paragraph, so it gets added
-to the paragraph's text:
--> document
- -> block_quote
- -> paragraph
- "Lorem ipsum dolor\nsit amet."
-
-The third line,
-> - Qui *quodsi iracundia*
-
-causes the paragraph block to be closed, and a new list block
-opened as a child of the block_quote. A list_item is also
-added as a child of the list, and a paragraph as a child of
-the list_item. The text is then added to the new paragraph:
--> document
- -> block_quote
- paragraph
- "Lorem ipsum dolor\nsit amet."
- -> list (type=bullet tight=true bullet_char=-)
- -> list_item
- -> paragraph
- "Qui *quodsi iracundia*"
-
-The fourth line,
-> - aliquando id
-
-causes the list_item (and its child the paragraph) to be closed,
-and a new list_item opened up as child of the list. A paragraph
-is added as a child of the new list_item, to contain the text.
-We thus obtain the final tree:
--> document
- -> block_quote
- paragraph
- "Lorem ipsum dolor\nsit amet."
- -> list (type=bullet tight=true bullet_char=-)
- list_item
- paragraph
- "Qui *quodsi iracundia*"
- -> list_item
- -> paragraph
- "aliquando id"
-
-Phase 2: inline structure
-Once all of the input has been parsed, all open blocks are closed.
-We then "walk the tree," visiting every node, and parse raw
-string contents of paragraphs and headings as inlines. At this
-point we have seen all the link reference definitions, so we can
-resolve reference links as we go.
-document
- block_quote
- paragraph
- str "Lorem ipsum dolor"
- softbreak
- str "sit amet."
- list (type=bullet tight=true bullet_char=-)
- list_item
- paragraph
- str "Qui "
- emph
- str "quodsi iracundia"
- list_item
- paragraph
- str "aliquando id"
-
-Notice how the [line ending] in the first paragraph has
-been parsed as a softbreak, and the asterisks in the first list item
-have become an emph.
-An algorithm for parsing nested emphasis and links
-By far the trickiest part of inline parsing is handling emphasis,
-strong emphasis, links, and images. This is done using the following
-algorithm.
-When we're parsing inlines and we hit either
-
-- a run of
* or _ characters, or
-- a
[ or ![
-
-we insert a text node with these symbols as its literal content, and we
-add a pointer to this text node to the delimiter stack.
-The [delimiter stack] is a doubly linked list. Each
-element contains a pointer to a text node, plus information about
-
-- the type of delimiter (
[, ![, *, _)
-- the number of delimiters,
-- whether the delimiter is "active" (all are active to start), and
-- whether the delimiter is a potential opener, a potential closer,
-or both (which depends on what sort of characters precede
-and follow the delimiters).
-
-When we hit a ] character, we call the look for link or image
-procedure (see below).
-When we hit the end of the input, we call the process emphasis
-procedure (see below), with stack_bottom = NULL.
-look for link or image
-Starting at the top of the delimiter stack, we look backwards
-through the stack for an opening [ or ![ delimiter.
-
--
-
If we don't find one, we return a literal text node ].
-
--
-
If we do find one, but it's not active, we remove the inactive
-delimiter from the stack, and return a literal text node ].
-
--
-
If we find one and it's active, then we parse ahead to see if
-we have an inline link/image, reference link/image, compact reference
-link/image, or shortcut reference link/image.
-
-
-
-process emphasis
-Parameter stack_bottom sets a lower bound to how far we
-descend in the [delimiter stack]. If it is NULL, we can
-go all the way to the bottom. Otherwise, we stop before
-visiting stack_bottom.
-Let current_position point to the element on the [delimiter stack]
-just above stack_bottom (or the first element if stack_bottom
-is NULL).
-We keep track of the openers_bottom for each delimiter
-type (*, _) and each length of the closing delimiter run
-(modulo 3). Initialize this to stack_bottom.
-Then we repeat the following until we run out of potential
-closers:
-
--
-
Move current_position forward in the delimiter stack (if needed)
-until we find the first potential closer with delimiter * or _.
-(This will be the potential closer closest
-to the beginning of the input -- the first one in parse order.)
-
--
-
Now, look back in the stack (staying above stack_bottom and
-the openers_bottom for this delimiter type) for the
-first matching potential opener ("matching" means same delimiter).
-
--
-
If one is found:
-
--
-
Figure out whether we have emphasis or strong emphasis:
-if both closer and opener spans have length >= 2, we have
-strong, otherwise regular.
-
--
-
Insert an emph or strong emph node accordingly, after
-the text node corresponding to the opener.
-
--
-
Remove any delimiters between the opener and closer from
-the delimiter stack.
-
--
-
Remove 1 (for regular emph) or 2 (for strong emph) delimiters
-from the opening and closing text nodes. If they become empty
-as a result, remove them and remove the corresponding element
-of the delimiter stack. If the closing node is removed, reset
-current_position to the next element in the stack.
-
-
-
--
-
If none is found:
-
--
-
Set openers_bottom to the element before current_position.
-(We know that there are no openers for this kind of closer up to and
-including this point, so this puts a lower bound on future searches.)
-
--
-
If the closer at current_position is not a potential opener,
-remove it from the delimiter stack (since we know it can't
-be a closer either).
-
--
-
Advance current_position to the next element in the stack.
-
-
-
-
-After we're done, we remove all delimiters above stack_bottom from the
-delimiter stack.
diff --git a/tests/test_container/__init__.py b/tests/test_container/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_container/fixtures.md b/tests/test_container/fixtures.md
deleted file mode 100644
index 9475b6ae..00000000
--- a/tests/test_container/fixtures.md
+++ /dev/null
@@ -1,286 +0,0 @@
-
-Simple container
-.
-::: name
-*content*
-:::
-.
-
-.
-
-Delimiters too short
-.
-:: name
-*content*
-::
-.
-:: name
-content
-::
-.
-
-
-Could contain block elements too
-.
-::: name
-### heading
-
------------
-:::
-.
-
-
heading
-
-
-.
-
-
-Ending marker could be longer
-.
-::::: name :::::
- hello world
-::::::::::::::::
-.
-
-.
-
-
-Nested blocks
-.
-::::: name
-:::: name
-xxx
-::::
-:::::
-.
-
-.
-
-
-Incorrectly nested blocks
-.
-:::: name
-this block is closed with 5 markers below
-
-::::: name
-auto-closed block
-
-:::::
-::::
-.
-
-
this block is closed with 5 markers below
-
-
::::
-.
-
-
-Marker could be indented up to 3 spaces
-.
- ::: name
- content
- :::
- :::
-.
-
-.
-
-
-But that's a code block
-.
- ::: name
- content
- :::
-.
-::: name
-content
-:::
-
-.
-
-
-Some more indent checks
-.
- ::: name
- not a code block
-
- code block
- :::
-.
-
-
not a code block
-
code block
-
-
::: namename
-xxx
-:::
-.
-
-
-Containers self-close at the end of the document
-.
-::: name
-xxx
-.
-
-.
-
-
-They should terminate paragraphs
-.
-blah blah
-::: name
-content
-:::
-.
-blah blah
-
-.
-
-
-They could be nested in lists
-.
- - ::: name
- - xxx
- :::
-.
-
-.
-
-
-Or in blockquotes
-.
-> ::: name
-> xxx
->> yyy
-> zzz
-> :::
-.
-
-
-
-.
-
-
-List indentation quirks
-.
- - ::: name
- xxx
- yyy
- :::
-
- - ::: name
- xxx
- yyy
- :::
-.
-
-:::
-
-yyy
-:::
-.
diff --git a/tests/test_container/test_container.py b/tests/test_container/test_container.py
deleted file mode 100644
index f601152a..00000000
--- a/tests/test_container/test_container.py
+++ /dev/null
@@ -1,18 +0,0 @@
-from textwrap import dedent
-
-from markdown_it import MarkdownIt
-from markdown_it.extensions.container import container_plugin
-
-
-def test_plugin_parse(data_regression):
- md = MarkdownIt().use(container_plugin, "name")
- tokens = md.parse(
- dedent(
- """\
- ::: name
- *content*
- :::
- """
- )
- )
- data_regression.check([t.as_dict() for t in tokens])
diff --git a/tests/test_container/test_container/test_plugin_parse.yml b/tests/test_container/test_container/test_plugin_parse.yml
deleted file mode 100644
index c744be7d..00000000
--- a/tests/test_container/test_container/test_plugin_parse.yml
+++ /dev/null
@@ -1,110 +0,0 @@
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ' name'
- level: 0
- map:
- - 0
- - 2
- markup: ':::'
- meta: {}
- nesting: 1
- tag: div
- type: container_name_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 1
- - 2
- markup: ''
- meta: {}
- nesting: 1
- tag: p
- type: paragraph_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map: null
- markup: '*'
- meta: {}
- nesting: 1
- tag: em
- type: em_open
- - attrs: null
- block: false
- children: null
- content: content
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- - attrs: null
- block: false
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map: null
- markup: '*'
- meta: {}
- nesting: -1
- tag: em
- type: em_close
- content: '*content*'
- hidden: false
- info: ''
- level: 2
- map:
- - 1
- - 2
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: p
- type: paragraph_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ':::'
- meta: {}
- nesting: -1
- tag: div
- type: container_name_close
diff --git a/tests/test_container/test_fixtures.py b/tests/test_container/test_fixtures.py
deleted file mode 100644
index 8e3a7695..00000000
--- a/tests/test_container/test_fixtures.py
+++ /dev/null
@@ -1,18 +0,0 @@
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.utils import read_fixture_file
-from markdown_it.extensions.container import container_plugin
-
-FIXTURE_PATH = Path(__file__).parent.joinpath("fixtures.md")
-
-
-@pytest.mark.parametrize("line,title,input,expected", read_fixture_file(FIXTURE_PATH))
-def test_all(line, title, input, expected):
- md = MarkdownIt("commonmark").use(container_plugin, "name")
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
diff --git a/tests/test_deflist/__init__.py b/tests/test_deflist/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_deflist/fixtures.md b/tests/test_deflist/fixtures.md
deleted file mode 100644
index a1fde516..00000000
--- a/tests/test_deflist/fixtures.md
+++ /dev/null
@@ -1,250 +0,0 @@
-
-Pandoc (with slightly changed indents):
-
-.
-Term 1
-
-: Definition 1
-
-Term 2 with *inline markup*
-
-: Definition 2
-
- { some code, part of Definition 2 }
-
- Third paragraph of definition 2.
-.
-
-- Term 1
--
-
Definition 1
-
-- Term 2 with inline markup
--
-
Definition 2
-{ some code, part of Definition 2 }
-
-Third paragraph of definition 2.
-
-
-.
-
-Pandoc again:
-
-.
-Term 1
-
-: Definition
-with lazy continuation.
-
- Second paragraph of the definition.
-.
-
-- Term 1
--
-
Definition
-with lazy continuation.
-Second paragraph of the definition.
-
-
-.
-
-Well, I might just copy-paste the third one while I'm at it:
-
-.
-Term 1
- ~ Definition 1
-
-Term 2
- ~ Definition 2a
- ~ Definition 2b
-.
-
-- Term 1
-- Definition 1
-- Term 2
-- Definition 2a
-- Definition 2b
-
-.
-
-Now, with our custom ones. Spaces after a colon:
-
-.
-Term 1
- : paragraph
-
-Term 2
- : code block
-.
-
-- Term 1
-- paragraph
-- Term 2
--
-
code block
-
-
-
-.
-
-There should be something after a colon by the way:
-
-.
-Non-term 1
- :
-
-Non-term 2
- :
-.
-Non-term 1
-:
-Non-term 2
-:
-.
-
-
-List is tight iff all dts are tight:
-.
-Term 1
-: foo
-: bar
-
-Term 2
-: foo
-
-: bar
-.
-
-- Term 1
--
-
foo
-
--
-
bar
-
-- Term 2
--
-
foo
-
--
-
bar
-
-
-.
-
-
-Regression test (first paragraphs shouldn't be tight):
-.
-Term 1
-: foo
-
- bar
-Term 2
-: foo
-.
-
-- Term 1
--
-
foo
-bar
-Term 2
-
--
-
foo
-
-
-.
-
-Definition lists should be second last in the queue. Exemplī grātiā, this isn't a valid one:
-
-.
-# test
- : just a paragraph with a colon
-.
-test
-: just a paragraph with a colon
-.
-
-Nested definition lists:
-
-.
-test
- : foo
- : bar
- : baz
- : bar
- : foo
-.
-
-- test
--
-
-- foo
--
-
-- bar
-- baz
-
-
-- bar
-
-
-- foo
-
-.
-
-
-Regression test, tabs
-.
-Term 1
- : code block
-.
-
-- Term 1
--
-
code block
-
-
-
-.
-
-
-Regression test (blockquote inside deflist)
-.
-foo
-: > bar
-
-: baz
-.
-
-- foo
--
-
-bar
-
-
--
-
baz
-
-
-.
-
-
-Coverage, 1 blank line
-.
-test
-
-.
-test
-.
-
-
-Coverage, 2 blank lines
-.
-test
-
-
-.
-test
-.
diff --git a/tests/test_deflist/test_deflist.py b/tests/test_deflist/test_deflist.py
deleted file mode 100644
index 48b1bafd..00000000
--- a/tests/test_deflist/test_deflist.py
+++ /dev/null
@@ -1,22 +0,0 @@
-from textwrap import dedent
-
-from markdown_it import MarkdownIt
-from markdown_it.extensions.deflist import deflist_plugin
-
-
-def test_plugin_parse(data_regression):
- md = MarkdownIt().use(deflist_plugin)
- tokens = md.parse(
- dedent(
- """\
- Term 1
-
- : Definition 1
-
- Term 2
- ~ Definition 2a
- ~ Definition 2b
- """
- )
- )
- data_regression.check([t.as_dict() for t in tokens])
diff --git a/tests/test_deflist/test_deflist/test_plugin_parse.yml b/tests/test_deflist/test_deflist/test_plugin_parse.yml
deleted file mode 100644
index 3202c2d0..00000000
--- a/tests/test_deflist/test_deflist/test_plugin_parse.yml
+++ /dev/null
@@ -1,392 +0,0 @@
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map:
- - 0
- - 7
- markup: ''
- meta: {}
- nesting: 1
- tag: dl
- type: dl_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 0
- - 0
- markup: ''
- meta: {}
- nesting: 1
- tag: dt
- type: dt_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: Term 1
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- content: Term 1
- hidden: false
- info: ''
- level: 2
- map:
- - 0
- - 0
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: dt
- type: dt_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 2
- - 4
- markup: ''
- meta: {}
- nesting: 1
- tag: dd
- type: dd_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map:
- - 2
- - 3
- markup: ''
- meta: {}
- nesting: 1
- tag: p
- type: paragraph_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: Definition 1
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- content: Definition 1
- hidden: false
- info: ''
- level: 3
- map:
- - 2
- - 3
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: p
- type: paragraph_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: dd
- type: dd_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 4
- - 4
- markup: ''
- meta: {}
- nesting: 1
- tag: dt
- type: dt_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: Term 2
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- content: Term 2
- hidden: false
- info: ''
- level: 2
- map:
- - 4
- - 4
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: dt
- type: dt_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 4
- - 6
- markup: ''
- meta: {}
- nesting: 1
- tag: dd
- type: dd_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map:
- - 5
- - 6
- markup: ''
- meta: {}
- nesting: 1
- tag: p
- type: paragraph_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: Definition 2a
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- content: Definition 2a
- hidden: false
- info: ''
- level: 3
- map:
- - 5
- - 6
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: p
- type: paragraph_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: dd
- type: dd_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 6
- - 7
- markup: ''
- meta: {}
- nesting: 1
- tag: dd
- type: dd_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map:
- - 6
- - 7
- markup: ''
- meta: {}
- nesting: 1
- tag: p
- type: paragraph_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: Definition 2b
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- content: Definition 2b
- hidden: false
- info: ''
- level: 3
- map:
- - 6
- - 7
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: p
- type: paragraph_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: dd
- type: dd_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: dl
- type: dl_close
diff --git a/tests/test_deflist/test_fixtures.py b/tests/test_deflist/test_fixtures.py
deleted file mode 100644
index 22be3a12..00000000
--- a/tests/test_deflist/test_fixtures.py
+++ /dev/null
@@ -1,18 +0,0 @@
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.utils import read_fixture_file
-from markdown_it.extensions.deflist import deflist_plugin
-
-FIXTURE_PATH = Path(__file__).parent.joinpath("fixtures.md")
-
-
-@pytest.mark.parametrize("line,title,input,expected", read_fixture_file(FIXTURE_PATH))
-def test_all(line, title, input, expected):
- md = MarkdownIt("commonmark").use(deflist_plugin)
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
diff --git a/tests/test_footnote/__init__.py b/tests/test_footnote/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_footnote/fixtures.md b/tests/test_footnote/fixtures.md
deleted file mode 100644
index 7ffeb8bf..00000000
--- a/tests/test_footnote/fixtures.md
+++ /dev/null
@@ -1,300 +0,0 @@
-
-Pandoc example:
-.
-Here is a footnote reference,[^1] and another.[^longnote]
-
-[^1]: Here is the footnote.
-
-[^longnote]: Here's one with multiple blocks.
-
- Subsequent paragraphs are indented to show that they
-belong to the previous footnote.
-
- { some.code }
-
- The whole paragraph can be indented, or just the first
- line. In this way, multi-paragraph footnotes work like
- multi-paragraph list items.
-
-This paragraph won't be part of the note, because it
-isn't indented.
-.
-Here is a footnote reference, and another.
-This paragraph won't be part of the note, because it
-isn't indented.
-
-
-.
-
-
-
-They could terminate each other:
-
-.
-[^1][^2][^3]
-
-[^1]: foo
-[^2]: bar
-[^3]: baz
-.
-
-
-
-.
-
-
-They could be inside blockquotes, and are lazy:
-.
-[^foo]
-
-> [^foo]: bar
-baz
-.
-
-
-
-
-.
-
-
-Their labels could not contain spaces or newlines:
-
-.
-[^ foo]: bar baz
-
-[^foo
-]: bar baz
-.
-[^ foo]: bar baz
-[^foo
-]: bar baz
-.
-
-
-We support inline notes too (pandoc example):
-
-.
-Here is an inline note.^[Inlines notes are easier to write, since
-you don't have to pick an identifier and move down to type the
-note.]
-.
-Here is an inline note.
-
-
-.
-
-
-They could have arbitrary markup:
-
-.
-foo^[ *bar* ]
-.
-foo
-
-
-.
-
-
-Duplicate footnotes:
-.
-[^xxxxx] [^xxxxx]
-
-[^xxxxx]: foo
-.
-
-
-
-.
-
-
-Indents:
-
-.
-[^xxxxx] [^yyyyy]
-
-[^xxxxx]: foo
- ---
-
-[^yyyyy]: foo
- ---
-.
-
-
-
-
-.
-
-
-Indents for the first line:
-
-.
-[^xxxxx] [^yyyyy]
-
-[^xxxxx]: foo
-
-[^yyyyy]: foo
-.
-
-
-
-.
-
-Indents for the first line (tabs):
-.
-[^xxxxx]
-
-[^xxxxx]: foo
-.
-
-
-
-.
-
-
-Security 1
-.
-[^__proto__]
-
-[^__proto__]: blah
-.
-
-
-
-.
-
-
-Security 2
-.
-[^hasOwnProperty]
-
-[^hasOwnProperty]: blah
-.
-
-
-
-.
-
-
-Should allow links in inline footnotes
-.
-Example^[this is another example https://github.com]
-.
-Example
-
-
-.
-
-Nested blocks:
-.
-[^a]
-
-[^a]: abc
-
- def
-hij
-
- - list
-
- > block
-
-terminates here
-.
-
-terminates here
-
-
-.
\ No newline at end of file
diff --git a/tests/test_footnote/test_fixtures.py b/tests/test_footnote/test_fixtures.py
deleted file mode 100644
index 02d192c8..00000000
--- a/tests/test_footnote/test_fixtures.py
+++ /dev/null
@@ -1,20 +0,0 @@
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.utils import read_fixture_file
-from markdown_it.extensions.footnote import footnote_plugin
-
-FIXTURE_PATH = Path(__file__).parent.joinpath("fixtures.md")
-
-
-@pytest.mark.parametrize("line,title,input,expected", read_fixture_file(FIXTURE_PATH))
-def test_all(line, title, input, expected):
- md = MarkdownIt("commonmark").use(footnote_plugin)
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip().replace("↩︎", "<-").replace(
- "↩", "<-"
- ) == expected.rstrip().replace("↩︎", "<-").replace("↩", "<-")
diff --git a/tests/test_footnote/test_footnote.py b/tests/test_footnote/test_footnote.py
deleted file mode 100644
index 9cd60e7a..00000000
--- a/tests/test_footnote/test_footnote.py
+++ /dev/null
@@ -1,464 +0,0 @@
-from textwrap import dedent
-
-from markdown_it import MarkdownIt
-from markdown_it.token import Token
-from markdown_it.rules_inline import StateInline
-from markdown_it.rules_block import StateBlock
-from markdown_it.extensions.footnote import index
-from markdown_it.extensions.footnote import footnote_plugin
-
-
-def test_footnote_def():
-
- md = MarkdownIt()
- src = r"[^a]: xyz"
- tokens = []
- state = StateBlock(src, md, {}, tokens)
- index.footnote_def(state, 0, 1, False)
- assert [t.as_dict() for t in tokens] == [
- {
- "type": "footnote_reference_open",
- "tag": "",
- "nesting": 1,
- "attrs": None,
- "map": [0, 1],
- "level": 0,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {"label": "a"},
- "block": False,
- "hidden": False,
- },
- {
- "type": "paragraph_open",
- "tag": "p",
- "nesting": 1,
- "attrs": None,
- "map": [0, 1],
- "level": 1,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {},
- "block": True,
- "hidden": False,
- },
- {
- "type": "inline",
- "tag": "",
- "nesting": 0,
- "attrs": None,
- "map": [0, 1],
- "level": 2,
- "children": [],
- "content": "xyz",
- "markup": "",
- "info": "",
- "meta": {},
- "block": True,
- "hidden": False,
- },
- {
- "type": "paragraph_close",
- "tag": "p",
- "nesting": -1,
- "attrs": None,
- "map": None,
- "level": 1,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {},
- "block": True,
- "hidden": False,
- },
- {
- "type": "footnote_reference_close",
- "tag": "",
- "nesting": -1,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {},
- "block": False,
- "hidden": False,
- },
- ]
- assert state.env == {"footnotes": {"refs": {":a": -1}}}
-
-
-def test_footnote_ref():
-
- md = MarkdownIt()
- src = r"[^a]"
- tokens = []
- state = StateInline(src, md, {}, tokens)
- state.env = {"footnotes": {"refs": {":a": -1}}}
- index.footnote_ref(state, False)
- # print([t.as_dict() for t in tokens])
- assert [t.as_dict() for t in tokens] == [
- {
- "type": "footnote_ref",
- "tag": "",
- "nesting": 0,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {"id": 0, "subId": 0, "label": "a"},
- "block": False,
- "hidden": False,
- }
- ]
- assert state.env == {
- "footnotes": {"refs": {":a": 0}, "list": {0: {"label": "a", "count": 1}}}
- }
-
-
-def test_footnote_inline():
-
- md = MarkdownIt().use(footnote_plugin)
- src = r"^[a]"
- tokens = []
- state = StateInline(src, md, {}, tokens)
- state.env = {"footnotes": {"refs": {":a": -1}}}
- index.footnote_inline(state, False)
- # print([t.as_dict() for t in tokens])
- assert [t.as_dict() for t in tokens] == [
- {
- "type": "footnote_ref",
- "tag": "",
- "nesting": 0,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {"id": 0},
- "block": False,
- "hidden": False,
- }
- ]
- assert state.env == {
- "footnotes": {
- "refs": {":a": -1},
- "list": {
- 0: {
- "content": "a",
- "tokens": [
- Token(
- type="text",
- tag="",
- nesting=0,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="a",
- markup="",
- info="",
- meta={},
- block=False,
- hidden=False,
- )
- ],
- }
- },
- }
- }
-
-
-def test_footnote_tail():
- md = MarkdownIt()
-
- tokens = [
- Token(
- **{
- "type": "footnote_reference_open",
- "tag": "",
- "nesting": 1,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {"label": "a"},
- "block": False,
- "hidden": False,
- }
- ),
- Token(
- **{
- "type": "paragraph_open",
- "tag": "p",
- "nesting": 1,
- "attrs": None,
- "map": [0, 1],
- "level": 1,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {},
- "block": True,
- "hidden": False,
- }
- ),
- Token(
- **{
- "type": "inline",
- "tag": "",
- "nesting": 0,
- "attrs": None,
- "map": [0, 1],
- "level": 2,
- "children": [],
- "content": "xyz",
- "markup": "",
- "info": "",
- "meta": {},
- "block": True,
- "hidden": False,
- }
- ),
- Token(
- **{
- "type": "paragraph_close",
- "tag": "p",
- "nesting": -1,
- "attrs": None,
- "map": None,
- "level": 1,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {},
- "block": True,
- "hidden": False,
- }
- ),
- Token(
- **{
- "type": "footnote_reference_close",
- "tag": "",
- "nesting": -1,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "",
- "markup": "",
- "info": "",
- "meta": {},
- "block": False,
- "hidden": False,
- }
- ),
- Token("other", "", 0),
- ]
- env = {"footnotes": {"refs": {":a": 0}, "list": {0: {"label": "a", "count": 1}}}}
- state = StateBlock("", md, env, tokens)
- index.footnote_tail(state)
- assert state.tokens == [
- Token(
- type="other",
- tag="",
- nesting=0,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=False,
- hidden=False,
- ),
- Token(
- type="footnote_block_open",
- tag="",
- nesting=1,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=False,
- hidden=False,
- ),
- Token(
- type="footnote_open",
- tag="",
- nesting=1,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={"id": 0, "label": "a"},
- block=False,
- hidden=False,
- ),
- Token(
- type="paragraph_open",
- tag="p",
- nesting=1,
- attrs=None,
- map=[0, 1],
- level=1,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=True,
- hidden=False,
- ),
- Token(
- type="inline",
- tag="",
- nesting=0,
- attrs=None,
- map=[0, 1],
- level=2,
- children=[],
- content="xyz",
- markup="",
- info="",
- meta={},
- block=True,
- hidden=False,
- ),
- Token(
- type="footnote_anchor",
- tag="",
- nesting=0,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={"id": 0, "subId": 0, "label": "a"},
- block=False,
- hidden=False,
- ),
- Token(
- type="paragraph_close",
- tag="p",
- nesting=-1,
- attrs=None,
- map=None,
- level=1,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=True,
- hidden=False,
- ),
- Token(
- type="footnote_close",
- tag="",
- nesting=-1,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=False,
- hidden=False,
- ),
- Token(
- type="footnote_block_close",
- tag="",
- nesting=-1,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=False,
- hidden=False,
- ),
- ]
-
-
-def test_plugin_render():
- md = MarkdownIt().use(footnote_plugin)
- text = md.render(
- dedent(
- """\
- [^1] ^[a] [^a] [^a]
-
- [^1]: abc
- [^a]: xyz
- """
- )
- )
- assert text == (
- dedent(
- """\
-
-
-
- """ # noqa: E501
- )
- )
-
-
-# def test_plugin_other():
-# md = MarkdownIt().use(footnote_plugin)
-# env = {}
-# tokens = md.parse(
-# dedent(
-# """\
-# [^xxxxx] [^xxxxx]
-
-# [^xxxxx]: foo
-# """
-# ),
-# env=env,
-# )
-# for t in tokens:
-# if "footnote" in t.type:
-# print(t)
diff --git a/tests/test_front_matter/__init__.py b/tests/test_front_matter/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_front_matter/fixtures.md b/tests/test_front_matter/fixtures.md
deleted file mode 100644
index e01fd4e7..00000000
--- a/tests/test_front_matter/fixtures.md
+++ /dev/null
@@ -1,87 +0,0 @@
-
-should parse empty front matter:
-.
----
----
-# Head
-.
-
-Head
-.
-
-
-should parse basic front matter:
-.
----
-x: 1
----
-# Head
-.
-
-Head
-.
-
-should parse until triple dots:
-.
----
-x: 1
-...
-# Head
-.
-
-Head
-.
-
-should parse front matter with indentation:
-.
----
-title: Associative arrays
-people:
- name: John Smith
- age: 33
-morePeople: { name: Grace Jones, age: 21 }
----
-# Head
-.
-
-Head
-.
-
-should ignore spaces after front matter delimiters:
-.
----
-title: Associative arrays
-people:
- name: John Smith
- age: 33
-morePeople: { name: Grace Jones, age: 21 }
----
-# Head
-.
-
-Head
-.
-
-should ignore front matter with less than 3 opening dashes:
-.
---
-x: 1
---
-# Head
-.
---
-x: 1
-Head
-.
-
-should require front matter have matching number of opening and closing dashes:
-.
-----
-x: 1
----
-# Head
-.
-
-x: 1
-Head
-.
diff --git a/tests/test_front_matter/test_fixtures.py b/tests/test_front_matter/test_fixtures.py
deleted file mode 100644
index 753ab84b..00000000
--- a/tests/test_front_matter/test_fixtures.py
+++ /dev/null
@@ -1,42 +0,0 @@
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.token import Token
-from markdown_it.utils import read_fixture_file
-from markdown_it.extensions.front_matter import front_matter_plugin
-
-FIXTURE_PATH = Path(__file__).parent.joinpath("fixtures.md")
-
-
-@pytest.mark.parametrize("line,title,input,expected", read_fixture_file(FIXTURE_PATH))
-def test_all(line, title, input, expected):
- md = MarkdownIt("commonmark").use(front_matter_plugin)
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
-
-
-def test_token():
- md = MarkdownIt("commonmark").use(front_matter_plugin)
- tokens = md.parse("---\na: 1\n---")
- # print(tokens)
- assert tokens == [
- Token(
- type="front_matter",
- tag="",
- nesting=0,
- attrs=None,
- map=[0, 3],
- level=0,
- children=None,
- content="a: 1",
- markup="---",
- info="",
- meta="a: 1",
- block=True,
- hidden=True,
- )
- ]
diff --git a/tests/test_math/__init__.py b/tests/test_math/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_math/fixtures_bracket.md b/tests/test_math/fixtures_bracket.md
deleted file mode 100644
index 330f4cb1..00000000
--- a/tests/test_math/fixtures_bracket.md
+++ /dev/null
@@ -1,387 +0,0 @@
-single character inline equation. (valid=True)
-.
-\(a\)
-.
-a
-.
-
-inline equation with single greek character (valid=True)
-.
-\(\\varphi\)
-.
-\\varphi
-.
-
-simple equation starting and ending with numbers. (valid=True)
-.
-\(1+1=2\)
-.
-1+1=2
-.
-
-simple equation including special html character. (valid=True)
-.
-\(1+1<3\)
-.
-1+1<3
-.
-
-equation including backslashes. (valid=True)
-.
-\(a \\backslash\)
-.
-a \\backslash
-.
-
-use of currency symbol (valid=True)
-.
-You get 3$ if you solve \(1+2\)
-.
-You get 3$ if you solve 1+2
-.
-
-use of currency symbol (valid=True)
-.
-If you solve \(1+2\) you get $3
-.
-If you solve 1+2 you get $3
-.
-
-inline fraction (valid=True)
-.
-\(\\frac{1}{2}\)
-.
-\\frac{1}{2}
-.
-
-inline column vector (valid=True)
-.
-\(\\begin{pmatrix}x\\\\y\\end{pmatrix}\)
-.
-\\begin{pmatrix}x\\\\y\\end{pmatrix}
-.
-
-inline bold vector notation (valid=True)
-.
-\({\\tilde\\bold e}_\\alpha\)
-.
-{\\tilde\\bold e}_\\alpha
-.
-
-exponentiation (valid=True)
-.
-\(a^{b}\)
-.
-a^{b}
-.
-
-conjugate complex (valid=True)
-.
-\(a^\*b\) with \(a^\*\)
-.
-a^\*b with a^\*
-.
-
-Inline multi-line (valid=True)
-.
-a \(a
-\not=1\) b
-.
-a a
-\not=1 b
-.
-
-Inline multi-line with newline (valid=False)
-.
-a \(a
-
-\not=1\) b
-.
-a (a
-\not=1) b
-.
-
-single block equation, greek index (valid=True)
-.
-\[e_\\alpha\]
-.
-
-.
-
-display equation on its own single line. (valid=True)
-.
-\[1+1=2\]
-.
-
-.
-
-inline equation followed by block equation. (valid=True)
-.
-\({e}_x\)
-
-\[e_\\alpha\]
-.
-{e}_x
-
-.
-
-underline tests (valid=True)
-.
-\[c{\\bold e}_x = a{\\bold e}_\\alpha - b\\tilde{\\bold e}_\\alpha\]
-.
-
-c{\\bold e}_x = a{\\bold e}_\\alpha - b\\tilde{\\bold e}_\\alpha
-
-.
-
-non-numeric character before opening $ or
-after closing $ or both is allowed. (valid=True)
-.
-a\(1+1=2\)
-\(1+1=2\)b
-c\(x\)d
-.
-a1+1=2
-1+1=2b
-cxd
-.
-
-following dollar character '$' is allowed. (valid=True)
-.
-\(x\) $
-.
-x $
-.
-
-consecutive inline equations. (valid=True)
-.
-\(x\) \(y\)
-.
-x y
-.
-
-inline equation after '-' sign in text. (valid=True)
-.
-so-what is \(x\)
-.
-so-what is x
-.
-
-display equation with line breaks. (valid=True)
-.
-\[
-1+1=2
-\]
-.
-
-.
-
-multiple equations (valid=True)
-.
-\[
-a = 1
-\]
-
-\[
-b = 2
-\]
-.
-
-
-.
-
-equation followed by a labelled equation (valid=True)
-.
-\[
-a = 1
-\]
-
-\[
-b = 2
-\] (1)
-.
-
-
-.
-
-multiline equation. (valid=True)
-.
-\[\\begin{matrix}
- f & = & 2 + x + 3 \\
- & = & 5 + x
-\\end{matrix}\]
-.
-
-\\begin{matrix}
- f & = & 2 + x + 3 \\
- & = & 5 + x
-\\end{matrix}
-
-.
-
-vector equation. (valid=True)
-.
-\[\\begin{pmatrix}x_2 \\\\ y_2 \\end{pmatrix} =
-\\begin{pmatrix} A & B \\\\ C & D \\end{pmatrix}\\cdot
-\\begin{pmatrix} x_1 \\\\ y_1 \\end{pmatrix}\]
-.
-
-\\begin{pmatrix}x_2 \\\\ y_2 \\end{pmatrix} =
-\\begin{pmatrix} A & B \\\\ C & D \\end{pmatrix}\\cdot
-\\begin{pmatrix} x_1 \\\\ y_1 \\end{pmatrix}
-
-.
-
-display equation with equation number. (valid=True)
-.
-\[f(x) = x^2 - 1\] (1)
-.
-
-.
-
-inline equation following code section. (valid=True)
-.
-`code`\(a-b\)
-.
-codea-b
-.
-
-equation following code block. (valid=True)
-.
-```
-code
-```
-\[a+b\]
-.
-code
-
-
-.
-
-numbered equation following code block. (valid=True)
-.
-```
-code
-```
-\[a+b\](1)
-.
-code
-
-
-.
-
-Equations in list. (valid=True)
-.
-1. \(1+2\)
-2. \(2+3\)
- 1. \(3+4\)
-.
-
-- 1+2
-- 2+3
-
-- 3+4
-
-
-
-.
-
-Inline sum. (valid=True)
-.
-\(\\sum\_{i=1}^n\)
-.
-\\sum\_{i=1}^n
-.
-
-Sum without equation number. (valid=True)
-.
-\[\\sum\_{i=1}^n\]
-.
-
-.
-
-Sum with equation number. (valid=True)
-.
-\[\\sum\_{i=1}\^n\] \(2\)
-.
-
-.
-
-equation number always vertically aligned. (valid=True)
-.
-\[{\\bold e}(\\varphi) = \\begin{pmatrix}
-\\cos\\varphi\\\\\\sin\\varphi
-\\end{pmatrix}\] (3)
-.
-
-{\\bold e}(\\varphi) = \\begin{pmatrix}
-\\cos\\varphi\\\\\\sin\\varphi
-\\end{pmatrix}
-
-.
-
-inline equations in blockquote. (valid=True)
-.
-> see \(a = b + c\)
-> \(c^2=a^2+b^2\) (2)
-> \(c^2=a^2+b^2\)
-.
-
-see a = b + c
-c^2=a^2+b^2 (2)
-c^2=a^2+b^2
-
-.
-
-display equation in blockquote. (valid=True)
-.
-> formula
->
-> \[ a+b=c\] (2)
->
-> in blockquote.
-.
-
-formula
-
-in blockquote.
-
-.
diff --git a/tests/test_math/fixtures_dollar.md b/tests/test_math/fixtures_dollar.md
deleted file mode 100644
index bada6fe6..00000000
--- a/tests/test_math/fixtures_dollar.md
+++ /dev/null
@@ -1,438 +0,0 @@
-single character inline equation. (valid=True)
-.
-$a$
-.
-a
-.
-
-inline equation with single greek character (valid=True)
-.
-$\\varphi$
-.
-\\varphi
-.
-
-simple equation starting and ending with numbers. (valid=True)
-.
-$1+1=2$
-.
-1+1=2
-.
-
-simple equation including special html character. (valid=True)
-.
-$1+1<3$
-.
-1+1<3
-.
-
-equation including backslashes. (valid=True)
-.
-$a \\backslash$
-.
-a \\backslash
-.
-
-use of currency symbol (valid=True)
-.
-You get 3$ if you solve $1+2$
-.
-You get 3$ if you solve 1+2
-.
-
-use of currency symbol (valid=True)
-.
-If you solve $1+2$ you get $3
-.
-If you solve 1+2 you get $3
-.
-
-inline fraction (valid=True)
-.
-$\\frac{1}{2}$
-.
-\\frac{1}{2}
-.
-
-inline column vector (valid=True)
-.
-$\\begin{pmatrix}x\\\\y\\end{pmatrix}$
-.
-\\begin{pmatrix}x\\\\y\\end{pmatrix}
-.
-
-inline bold vector notation (valid=True)
-.
-${\\tilde\\bold e}_\\alpha$
-.
-{\\tilde\\bold e}_\\alpha
-.
-
-exponentiation (valid=True)
-.
-$a^{b}$
-.
-a^{b}
-.
-
-conjugate complex (valid=True)
-.
-$a^\*b$ with $a^\*$
-.
-a^\*b with a^\*
-.
-
-Inline multi-line (valid=True)
-.
-a $a
-\not=1$ b
-.
-a a
-\not=1 b
-.
-
-Inline multi-line with newline (valid=False)
-.
-a $a
-
-\not=1$ b
-.
-a $a
-\not=1$ b
-.
-
-single block equation, greek index (valid=True)
-.
-$$e_\\alpha$$
-.
-
-.
-
-display equation on its own single line. (valid=True)
-.
-$$1+1=2$$
-.
-
-.
-
-inline equation followed by block equation. (valid=True)
-.
-${e}_x$
-
-$$e_\\alpha$$
-.
-{e}_x
-
-.
-
-underline tests (valid=True)
-.
-$$c{\\bold e}_x = a{\\bold e}_\\alpha - b\\tilde{\\bold e}_\\alpha$$
-.
-
-c{\\bold e}_x = a{\\bold e}_\\alpha - b\\tilde{\\bold e}_\\alpha
-
-.
-
-non-numeric character before opening $ or
-after closing $ or both is allowed. (valid=True)
-.
-a$1+1=2$
-$1+1=2$b
-c$x$d
-.
-a1+1=2
-1+1=2b
-cxd
-.
-
-following dollar character '$' is allowed. (valid=True)
-.
-$x$ $
-.
-x $
-.
-
-consecutive inline equations. (valid=True)
-.
-$x$ $y$
-.
-x y
-.
-
-inline equation after '-' sign in text. (valid=True)
-.
-so-what is $x$
-.
-so-what is x
-.
-
-display equation with line breaks. (valid=True)
-.
-$$
-1+1=2
-$$
-.
-
-.
-
-multiple equations (valid=True)
-.
-$$
-a = 1
-$$
-
-$$
-b = 2
-$$
-.
-
-
-.
-
-equation followed by a labelled equation (valid=True)
-.
-$$
-a = 1
-$$
-
-$$
-b = 2
-$$ (1)
-.
-
-
-.
-
-multiline equation. (valid=True)
-.
-$$\\begin{matrix}
- f & = & 2 + x + 3 \\
- & = & 5 + x
-\\end{matrix}$$
-.
-
-\\begin{matrix}
- f & = & 2 + x + 3 \\
- & = & 5 + x
-\\end{matrix}
-
-.
-
-vector equation. (valid=True)
-.
-$$\\begin{pmatrix}x_2 \\\\ y_2 \\end{pmatrix} =
-\\begin{pmatrix} A & B \\\\ C & D \\end{pmatrix}\\cdot
-\\begin{pmatrix} x_1 \\\\ y_1 \\end{pmatrix}$$
-.
-
-\\begin{pmatrix}x_2 \\\\ y_2 \\end{pmatrix} =
-\\begin{pmatrix} A & B \\\\ C & D \\end{pmatrix}\\cdot
-\\begin{pmatrix} x_1 \\\\ y_1 \\end{pmatrix}
-
-.
-
-display equation with equation number. (valid=True)
-.
-$$f(x) = x^2 - 1$$ (1)
-.
-
-.
-
-inline equation following code section. (valid=True)
-.
-`code`$a-b$
-.
-codea-b
-.
-
-equation following code block. (valid=True)
-.
-```
-code
-```
-$$a+b$$
-.
-code
-
-
-.
-
-numbered equation following code block. (valid=True)
-.
-```
-code
-```
-$$a+b$$(1)
-.
-code
-
-
-.
-
-Equations in list. (valid=True)
-.
-1. $1+2$
-2. $2+3$
- 1. $3+4$
-.
-
-- 1+2
-- 2+3
-
-- 3+4
-
-
-
-.
-
-Inline sum. (valid=True)
-.
-$\\sum\_{i=1}^n$
-.
-\\sum\_{i=1}^n
-.
-
-Sum without equation number. (valid=True)
-.
-$$\\sum\_{i=1}^n$$
-.
-
-.
-
-Sum with equation number. (valid=True)
-.
-$$\\sum\_{i=1}\^n$$ \(2\)
-.
-
-.
-
-equation number always vertically aligned. (valid=True)
-.
-$${\\bold e}(\\varphi) = \\begin{pmatrix}
-\\cos\\varphi\\\\\\sin\\varphi
-\\end{pmatrix}$$ (3)
-.
-
-{\\bold e}(\\varphi) = \\begin{pmatrix}
-\\cos\\varphi\\\\\\sin\\varphi
-\\end{pmatrix}
-
-.
-
-inline equations in blockquote. (valid=True)
-.
-> see $a = b + c$
-> $c^2=a^2+b^2$ (2)
-> $c^2=a^2+b^2$
-.
-
-see a = b + c
-c^2=a^2+b^2 (2)
-c^2=a^2+b^2
-
-.
-
-display equation in blockquote. (valid=True)
-.
-> formula
->
-> $$ a+b=c$$ (2)
->
-> in blockquote.
-.
-
-formula
-
-in blockquote.
-
-.
-
-mixed syntax:
-.
-$$
-a=1 \\
-b=2
-$$ (abc)
-
-- ab $c=1$ d
-.
-
-
-.
-
-escaped dollars '\\$' are interpreted as
-dollar '$' characters. (valid=True)
-.
-\\$1+1=2$
-$1+1=2\\$
-.
-\$1+1=2$
-$1+1=2\$
-.
-
-empty line between text and display formula is required. (valid=False)
-.
-some text
- \$\\$a+b=c\$\$
-.
-some text
-$\$a+b=c$$
-.
-
-whitespace character after opening $
-or before closing $ is not allowed. (valid=False)
-.
-$ $
-$ x$
-$x $
-.
-$ $
-$ x$
-$x $
-.
diff --git a/tests/test_math/test_math.py b/tests/test_math/test_math.py
deleted file mode 100644
index c57d53eb..00000000
--- a/tests/test_math/test_math.py
+++ /dev/null
@@ -1,105 +0,0 @@
-from pathlib import Path
-from textwrap import dedent
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.rules_inline import StateInline
-from markdown_it.rules_block import StateBlock
-from markdown_it.extensions.texmath import index as main
-from markdown_it.extensions.texmath import texmath_plugin
-from markdown_it.utils import read_fixture_file
-
-FIXTURE_PATH = Path(__file__).parent
-
-
-def test_inline_func():
-
- inline_func = main.make_inline_func(main.rules.dollars.inline[0])
-
- md = MarkdownIt()
- src = r"$a=1$ $b=2$"
- tokens = []
- state = StateInline(src, md, {}, tokens)
- inline_func(state, False)
- assert tokens[0].as_dict() == {
- "type": "math_inline",
- "tag": "math",
- "nesting": 0,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "a=1",
- "markup": "$",
- "info": "",
- "meta": {},
- "block": False,
- "hidden": False,
- }
- assert state.pos == 5
-
-
-def test_block_func():
- block_func = main.make_block_func(main.rules.dollars.block[0])
- md = MarkdownIt()
- src = r"$$\na=1\n\nc\nb=2$$ (abc)"
- tokens = []
- state = StateBlock(src, md, {}, tokens)
- block_func(state, 0, 10, False)
- assert tokens[0].as_dict() == {
- "type": "math_block_eqno",
- "tag": "math",
- "nesting": 0,
- "attrs": None,
- "map": None,
- "level": 0,
- "children": None,
- "content": "\\na=1\\n\\nc\\nb=2",
- "markup": "$$",
- "info": "abc",
- "meta": {},
- "block": True,
- "hidden": False,
- }
-
-
-def test_plugin_parse(data_regression):
- md = MarkdownIt().use(texmath_plugin)
- tokens = md.parse(
- dedent(
- """\
- $$
- a=1
- b=2
- $$ (abc)
-
- - ab $c=1$ d
- """
- )
- )
- data_regression.check([t.as_dict() for t in tokens])
-
-
-@pytest.mark.parametrize(
- "line,title,input,expected",
- read_fixture_file(FIXTURE_PATH.joinpath("fixtures_dollar.md")),
-)
-def test_dollar_fixtures(line, title, input, expected):
- md = MarkdownIt("commonmark").use(texmath_plugin)
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
-
-
-@pytest.mark.parametrize(
- "line,title,input,expected",
- read_fixture_file(FIXTURE_PATH.joinpath("fixtures_bracket.md")),
-)
-def test_bracket_fixtures(line, title, input, expected):
- md = MarkdownIt("commonmark").use(texmath_plugin, delimiters="brackets")
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
diff --git a/tests/test_math/test_math/test_plugin_parse.yml b/tests/test_math/test_math/test_plugin_parse.yml
deleted file mode 100644
index eac4e096..00000000
--- a/tests/test_math/test_math/test_plugin_parse.yml
+++ /dev/null
@@ -1,157 +0,0 @@
-- attrs: null
- block: true
- children: null
- content: '
-
- a=1
-
- b=2
-
- '
- hidden: false
- info: abc
- level: 0
- map: null
- markup: $$
- meta: {}
- nesting: 0
- tag: math
- type: math_block_eqno
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map:
- - 5
- - 6
- markup: '-'
- meta: {}
- nesting: 1
- tag: ul
- type: bullet_list_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map:
- - 5
- - 6
- markup: '-'
- meta: {}
- nesting: 1
- tag: li
- type: list_item_open
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map:
- - 5
- - 6
- markup: ''
- meta: {}
- nesting: 1
- tag: p
- type: paragraph_open
-- attrs: null
- block: true
- children:
- - attrs: null
- block: false
- children: null
- content: 'ab '
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- - attrs: null
- block: false
- children: null
- content: c=1
- hidden: false
- info: ''
- level: 0
- map: null
- markup: $
- meta: {}
- nesting: 0
- tag: math
- type: math_inline
- - attrs: null
- block: false
- children: null
- content: ' d'
- hidden: false
- info: ''
- level: 0
- map: null
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: text
- content: ab $c=1$ d
- hidden: false
- info: ''
- level: 3
- map:
- - 5
- - 6
- markup: ''
- meta: {}
- nesting: 0
- tag: ''
- type: inline
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: true
- info: ''
- level: 2
- map: null
- markup: ''
- meta: {}
- nesting: -1
- tag: p
- type: paragraph_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 1
- map: null
- markup: '-'
- meta: {}
- nesting: -1
- tag: li
- type: list_item_close
-- attrs: null
- block: true
- children: null
- content: ''
- hidden: false
- info: ''
- level: 0
- map: null
- markup: '-'
- meta: {}
- nesting: -1
- tag: ul
- type: bullet_list_close
diff --git a/tests/test_myst_block/__init__.py b/tests/test_myst_block/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_myst_block/fixtures.md b/tests/test_myst_block/fixtures.md
deleted file mode 100644
index 656c22a3..00000000
--- a/tests/test_myst_block/fixtures.md
+++ /dev/null
@@ -1,96 +0,0 @@
-
-Block Break:
-.
-+++
-.
-
-.
-
-Block Break Split Markers:
-.
- + + + + xfsdfsdf
-.
-
-.
-
-Block Break Too Few Markers:
-.
-++
-.
-++
-.
-
-Block Break terminates other blocks:
-.
-a
-+++
-- b
-+++
-> c
-+++
-.
-a
-
-
-
-
-c
-
-
-.
-
-
-Target:
-.
-(a)=
-.
-target = a
-.
-
-
-Target terminates other blocks:
-.
-a
-(a)=
-- b
-(a)=
-> c
-(a)=
-.
-a
-target = a
-target = a
-c
-
-target = a
-.
-
-Comment:
-.
-% abc
-.
-
-.
-
-Comment terminates other blocks:
-.
-a
-% abc
-- b
-% abc
-> c
-% abc
-.
-a
-
-
-c
-
-
-.
diff --git a/tests/test_myst_block/test_fixtures.py b/tests/test_myst_block/test_fixtures.py
deleted file mode 100644
index 26f8c5fc..00000000
--- a/tests/test_myst_block/test_fixtures.py
+++ /dev/null
@@ -1,82 +0,0 @@
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.token import Token
-from markdown_it.utils import read_fixture_file
-from markdown_it.extensions.myst_blocks import myst_block_plugin
-
-FIXTURE_PATH = Path(__file__).parent.joinpath("fixtures.md")
-
-
-@pytest.mark.parametrize("line,title,input,expected", read_fixture_file(FIXTURE_PATH))
-def test_all(line, title, input, expected):
- md = MarkdownIt("commonmark").use(myst_block_plugin)
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
-
-
-def test_block_token():
- md = MarkdownIt("commonmark").use(myst_block_plugin)
- tokens = md.parse("+++")
- assert tokens == [
- Token(
- type="myst_block_break",
- tag="hr",
- nesting=0,
- attrs=[["class", "myst-block"]],
- map=[0, 1],
- level=0,
- children=None,
- content="",
- markup="+++",
- info="",
- meta={},
- block=True,
- hidden=False,
- )
- ]
-
- tokens = md.parse("\n+ + + abc")
- assert tokens == [
- Token(
- type="myst_block_break",
- tag="hr",
- nesting=0,
- attrs=[["class", "myst-block"]],
- map=[1, 2],
- level=0,
- children=None,
- content="abc",
- markup="+++",
- info="",
- meta={},
- block=True,
- hidden=False,
- )
- ]
-
-
-def test_comment_token():
- md = MarkdownIt("commonmark").use(myst_block_plugin)
- tokens = md.parse("\n\n% abc")
- assert tokens == [
- Token(
- type="myst_line_comment",
- tag="",
- nesting=0,
- attrs=[["class", "myst-line-comment"]],
- map=[2, 3],
- level=0,
- children=None,
- content="abc",
- markup="%",
- info="",
- meta={},
- block=True,
- hidden=False,
- )
- ]
diff --git a/tests/test_myst_role/__init__.py b/tests/test_myst_role/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_myst_role/fixtures.md b/tests/test_myst_role/fixtures.md
deleted file mode 100644
index c0471935..00000000
--- a/tests/test_myst_role/fixtures.md
+++ /dev/null
@@ -1,75 +0,0 @@
-
-Basic:
-.
-{abc}`xyz`
-.
-{abc}[xyz]
-.
-
-Surrounding Text:
-.
-a {abc}`xyz` b
-.
-a {abc}[xyz] b
-.
-
-In Code:
-.
-`` {abc}`xyz` ``
-.
-{abc}`xyz`
-.
-
-
-Surrounding Code:
-.
-`a` {abc}`xyz` `b`
-.
-a {abc}[xyz] b
-.
-
-In list:
-.
-- {abc}`xyz`
-.
-
-.
-
-In Quote:
-.
-> {abc}`xyz` b
-.
-
-{abc}[xyz] b
-
-.
-
-Multiple ticks:
-.
-{abc}``xyz``
-.
-{abc}[xyz]
-.
-
-Unbalanced ticks:
-.
-{abc}``xyz`
-.
-{abc}``xyz`
-.
-
-Space in name:
-.
-{ab c}`xyz`
-.
-{ab c}xyz
-.
-
-Escaped:
-.
-\{abc}`xyz`
-.
-{abc}xyz
-.
diff --git a/tests/test_myst_role/test_fixtures.py b/tests/test_myst_role/test_fixtures.py
deleted file mode 100644
index 4aae6113..00000000
--- a/tests/test_myst_role/test_fixtures.py
+++ /dev/null
@@ -1,18 +0,0 @@
-from pathlib import Path
-
-import pytest
-
-from markdown_it import MarkdownIt
-from markdown_it.utils import read_fixture_file
-from markdown_it.extensions.myst_role import myst_role_plugin
-
-FIXTURE_PATH = Path(__file__).parent.joinpath("fixtures.md")
-
-
-@pytest.mark.parametrize("line,title,input,expected", read_fixture_file(FIXTURE_PATH))
-def test_all(line, title, input, expected):
- md = MarkdownIt("commonmark").use(myst_role_plugin)
- md.options["xhtmlOut"] = False
- text = md.render(input)
- print(text)
- assert text.rstrip() == expected.rstrip()
diff --git a/tests/test_myst_role/test_role.py b/tests/test_myst_role/test_role.py
deleted file mode 100644
index 43c1285a..00000000
--- a/tests/test_myst_role/test_role.py
+++ /dev/null
@@ -1,73 +0,0 @@
-from markdown_it import MarkdownIt
-from markdown_it.token import Token
-from markdown_it.extensions.myst_role import myst_role_plugin
-
-
-def test_basic():
- md = MarkdownIt().use(myst_role_plugin)
- src = "{abc}``` a ```"
- tokens = md.parse(src)
- print(tokens)
- assert tokens == [
- Token(
- type="paragraph_open",
- tag="p",
- nesting=1,
- attrs=None,
- map=[0, 1],
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=True,
- hidden=False,
- ),
- Token(
- type="inline",
- tag="",
- nesting=0,
- attrs=None,
- map=[0, 1],
- level=1,
- children=[
- Token(
- type="myst_role",
- tag="",
- nesting=0,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content=" a ",
- markup="",
- info="",
- meta={"name": "abc"},
- block=False,
- hidden=False,
- )
- ],
- content="{abc}``` a ```",
- markup="",
- info="",
- meta={},
- block=True,
- hidden=False,
- ),
- Token(
- type="paragraph_close",
- tag="p",
- nesting=-1,
- attrs=None,
- map=None,
- level=0,
- children=None,
- content="",
- markup="",
- info="",
- meta={},
- block=True,
- hidden=False,
- ),
- ]
diff --git a/tests/test_port/__init__.py b/tests/test_port/__init__.py
deleted file mode 100644
index e69de29b..00000000
diff --git a/tests/test_port/fixtures/commonmark_extras.md b/tests/test_port/fixtures/commonmark_extras.md
deleted file mode 100644
index 7bdd0b59..00000000
--- a/tests/test_port/fixtures/commonmark_extras.md
+++ /dev/null
@@ -1,524 +0,0 @@
-Issue #246. Double escaping in ALT
-.
-
-.
-
-.
-
-Strip markdown in ALT tags
-.
-](#)
-.
-
-.
-
-Issue #55:
-.
-![test]
-
-
-.
-![test]
-
-.
-
-
-Reference labels: 'i̇θωkå'.toUpperCase() is 'İΘΩKÅ', but these should still be equivalent
-.
-[İϴΩKÅ]
-
-[i̇θωkå]: /url
-.
-İϴΩKÅ
-.
-
-
-Reference labels: support ligatures (equivalent according to unicode case folding)
-.
-[fffifl]
-
-[fffifl]: /url
-.
-fffifl
-.
-
-
-Issue #35. `<` should work as punctuation
-.
-an **(:**
-.
-an (:
-.
-
-
-Should unescape only needed things in link destinations/titles:
-.
-[test](<\f\o\o\>\\>)
-
-[test](foo "\\\"\b\a\r")
-.
-test
-test
-.
-
-
-Not a closing tag
-.
-
-.
-</ 123>
-.
-
-
-
-Escaping entities in links:
-.
-[](<"> "&ö")
-
-[](<\"> "\&\ö")
-
-[](<\\"> "\\"\\ö")
-.
-
-
-
-.
-
-
-Checking combination of replaceEntities and unescapeMd:
-.
-~~~ &&bad;\&\\&
-just a funny little fence
-~~~
-.
-just a funny little fence
-
-.
-
-Underscore between punctuation chars should be able to close emphasis.
-
-.
-_(hai)_.
-.
-(hai).
-.
-
-Regression test, should not match emphasis markers in different link tags:
-.
-[*b]() [c*]()
-.
-*b c*
-.
-
-Those are two separate blockquotes:
-.
- - > foo
- > bar
-.
-
-
-bar
-
-.
-
-Blockquote should terminate itself after paragraph continuation
-.
-- list
- > blockquote
-blockquote continuation
- - next list item
-.
-
-- list
-
-blockquote
-blockquote continuation
-
-
-
-
-.
-
-Regression test (code block + regular paragraph)
-.
-> foo
-> bar
-.
-
-foo
-
-bar
-
-.
-
-Blockquotes inside indented lists should terminate correctly
-.
- - a
- > b
- ```
- c
- ```
- - d
-.
-
-.
-
-Don't output empty class here:
-.
-```
-test
-```
-.
-test
-
-.
-
-Setext header text supports lazy continuations:
-.
- - foo
-bar
- ===
-.
-
-.
-
-But setext header underline doesn't:
-.
- - foo
- bar
- ===
-.
-
-.
-
-Tabs should be stripped from the beginning of the line
-.
- foo
- bar
- baz
-.
-foo
-bar
-baz
-.
-
-Tabs should not cause hardbreak, EOL tabs aren't stripped in commonmark 0.27
-.
-foo1
-foo2
-bar
-.
-foo1
-foo2
-bar
-.
-
-List item terminating quote should not be paragraph continuation
-.
-1. foo
- > quote
-2. bar
-.
-
-- foo
-
-quote
-
-
-- bar
-
-.
-
-Coverage. Directive can terminate paragraph.
-.
-a
-a
-*
-.
-foo@bar.com
-.
-
-
-Coverage. Unpaired nested backtick (silent mode)
-.
-*`foo*
-.
-`foo
-.
-
-
-Coverage. Entities.
-.
-*&*
-
-* *
-
-*&*
-.
-&
-
-&
-.
-
-
-Coverage. Escape.
-.
-*\a*
-.
-\a
-.
-
-
-Coverage. parseLinkDestination
-.
-[foo](<
-bar>)
-
-[foo]([foo](<
-bar>)
-[foo](<bar)
-.
-
-
-Coverage. parseLinkTitle
-.
-[foo](bar "ba)
-
-[foo](bar "ba\
-z")
-.
-[foo](bar "ba)
-foo
-.
-
-
-Coverage. Image
-.
-
-.
-
-.
-.
-![test][foo]
-
-[bar]: 123
-.
-![test][foo]
-.
-.
-![test][[[
-
-[bar]: 123
-.
-![test][[[
-.
-.
-![test](
-.
-![test](
-.
-
-
-Coverage. Link
-.
-[test](
-.
-[test](
-.
-
-
-Coverage. Reference
-.
-[
-test\
-]: 123
-foo
-bar
-.
-foo
-bar
-.
-.
-[
-test
-]
-.
-[
-test
-]
-.
-.
-> [foo]: bar
-[foo]
-.
-
-foo
-.
-
-Coverage. Tabs in blockquotes.
-.
-> test
-
- > test
-
- > test
-
-> ---
-> test
-
- > ---
- > test
-
- > ---
- > test
-
-> test
-
- > test
-
- > test
-
-> ---
-> test
-
- > ---
- > test
-
- > ---
- > test
-.
-
- test
-
-
-
- test
-
-
-
-test
-
-
-
-
- test
-
-
-
-
- test
-
-
-
-
-test
-
-
-
- test
-
-
-
- test
-
-
-
- test
-
-
-
-
- test
-
-
-
-
- test
-
-
-
-
- test
-
-
-.
-
-Coverage. Tabs in lists.
-.
-1. foo
-
- bar
-.
-
--
-
foo
- bar
-
-
-
-.
-
-Coverage. Various tags not interrupting blockquotes because of indentation:
-.
-> foo
- - - - -
-
-> foo
- # not a heading
-.
-
-foo
-- - - -
-
-
-foo
-# not a heading
-
-.
-
-Coverage, entities with code > 10FFFF. Made this way for compatibility with commonmark.js.
-.
-�
-
-�
-.
-�
-�
-.
diff --git a/tests/test_port/fixtures/commonmark_spec.md b/tests/test_port/fixtures/commonmark_spec.md
deleted file mode 100644
index 889f3d80..00000000
--- a/tests/test_port/fixtures/commonmark_spec.md
+++ /dev/null
@@ -1,7794 +0,0 @@
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 351
-
-.
- foo baz bim
-.
-foo baz bim
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 358
-
-.
- foo baz bim
-.
-foo baz bim
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 365
-
-.
- a a
- ὐ a
-.
-a a
-ὐ a
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 378
-
-.
- - foo
-
- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 391
-
-.
-- foo
-
- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 414
-
-.
-> foo
-.
-
- foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 423
-
-.
-- foo
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 435
-
-.
- foo
- bar
-.
-foo
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 444
-
-.
- - foo
- - bar
- - baz
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 462
-
-.
-# Foo
-.
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 468
-
-.
-* * *
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 495
-
-.
-- `one
-- two`
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 534
-
-.
-***
----
-___
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 547
-
-.
-+++
-.
-+++
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 554
-
-.
-===
-.
-===
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 563
-
-.
---
-**
-__
-.
---
-**
-__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 576
-
-.
- ***
- ***
- ***
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 589
-
-.
- ***
-.
-***
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 597
-
-.
-Foo
- ***
-.
-Foo
-***
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 608
-
-.
-_____________________________________
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 617
-
-.
- - - -
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 624
-
-.
- ** * ** * ** * **
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 631
-
-.
-- - - -
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 640
-
-.
-- - - -
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 649
-
-.
-_ _ _ _ a
-
-a------
-
----a---
-.
-_ _ _ _ a
-a------
----a---
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 665
-
-.
- *-*
-.
--
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 674
-
-.
-- foo
-***
-- bar
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 691
-
-.
-Foo
-***
-bar
-.
-Foo
-
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 708
-
-.
-Foo
----
-bar
-.
-Foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 721
-
-.
-* Foo
-* * *
-* Bar
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 738
-
-.
-- Foo
-- * * *
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 767
-
-.
-# foo
-## foo
-### foo
-#### foo
-##### foo
-###### foo
-.
-foo
-foo
-foo
-foo
-foo
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 786
-
-.
-####### foo
-.
-####### foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 801
-
-.
-#5 bolt
-
-#hashtag
-.
-#5 bolt
-#hashtag
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 813
-
-.
-\## foo
-.
-## foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 822
-
-.
-# foo *bar* \*baz\*
-.
-foo bar *baz*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 831
-
-.
-# foo
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 840
-
-.
- ### foo
- ## foo
- # foo
-.
-foo
-foo
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 853
-
-.
- # foo
-.
-# foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 861
-
-.
-foo
- # bar
-.
-foo
-# bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 872
-
-.
-## foo ##
- ### bar ###
-.
-foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 883
-
-.
-# foo ##################################
-##### foo ##
-.
-foo
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 894
-
-.
-### foo ###
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 905
-
-.
-### foo ### b
-.
-foo ### b
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 914
-
-.
-# foo#
-.
-foo#
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 924
-
-.
-### foo \###
-## foo #\##
-# foo \#
-.
-foo ###
-foo ###
-foo #
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 938
-
-.
-****
-## foo
-****
-.
-
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 949
-
-.
-Foo bar
-# baz
-Bar foo
-.
-Foo bar
-baz
-Bar foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 962
-
-.
-##
-#
-### ###
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1005
-
-.
-Foo *bar*
-=========
-
-Foo *bar*
----------
-.
-Foo bar
-Foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1019
-
-.
-Foo *bar
-baz*
-====
-.
-Foo bar
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1033
-
-.
- Foo *bar
-baz*
-====
-.
-Foo bar
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1045
-
-.
-Foo
--------------------------
-
-Foo
-=
-.
-Foo
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1060
-
-.
- Foo
----
-
- Foo
------
-
- Foo
- ===
-.
-Foo
-Foo
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1078
-
-.
- Foo
- ---
-
- Foo
----
-.
-Foo
----
-
-Foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1097
-
-.
-Foo
- ----
-.
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1107
-
-.
-Foo
- ---
-.
-Foo
----
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1118
-
-.
-Foo
-= =
-
-Foo
---- -
-.
-Foo
-= =
-Foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1134
-
-.
-Foo
------
-.
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1144
-
-.
-Foo\
-----
-.
-Foo\
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1155
-
-.
-`Foo
-----
-`
-
-
-.
-`Foo
-`
-<a title="a lot
-of dashes"/>
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1174
-
-.
-> Foo
----
-.
-
-Foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1185
-
-.
-> foo
-bar
-===
-.
-
-foo
-bar
-===
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1198
-
-.
-- Foo
----
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1213
-
-.
-Foo
-Bar
----
-.
-Foo
-Bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1226
-
-.
----
-Foo
----
-Bar
----
-Baz
-.
-
-Foo
-Bar
-Baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1243
-
-.
-
-====
-.
-====
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1255
-
-.
----
----
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1264
-
-.
-- foo
------
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1275
-
-.
- foo
----
-.
-foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1285
-
-.
-> foo
------
-.
-
-foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1299
-
-.
-\> foo
-------
-.
-> foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1330
-
-.
-Foo
-
-bar
----
-baz
-.
-Foo
-bar
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1346
-
-.
-Foo
-bar
-
----
-
-baz
-.
-Foo
-bar
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1364
-
-.
-Foo
-bar
-* * *
-baz
-.
-Foo
-bar
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1379
-
-.
-Foo
-bar
-\---
-baz
-.
-Foo
-bar
----
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1407
-
-.
- a simple
- indented code block
-.
-a simple
- indented code block
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1421
-
-.
- - foo
-
- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1435
-
-.
-1. foo
-
- - bar
-.
-
--
-
foo
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1455
-
-.
-
- *hi*
-
- - one
-.
-<a/>
-*hi*
-
-- one
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1471
-
-.
- chunk1
-
- chunk2
-
-
-
- chunk3
-.
-chunk1
-
-chunk2
-
-
-
-chunk3
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1494
-
-.
- chunk1
-
- chunk2
-.
-chunk1
-
- chunk2
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1509
-
-.
-Foo
- bar
-
-.
-Foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1523
-
-.
- foo
-bar
-.
-foo
-
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1536
-
-.
-# Heading
- foo
-Heading
-------
- foo
-----
-.
-Heading
-foo
-
-Heading
-foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1556
-
-.
- foo
- bar
-.
- foo
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1569
-
-.
-
-
- foo
-
-
-.
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1583
-
-.
- foo
-.
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1638
-
-.
-```
-<
- >
-```
-.
-<
- >
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1652
-
-.
-~~~
-<
- >
-~~~
-.
-<
- >
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1665
-
-.
-``
-foo
-``
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1676
-
-.
-```
-aaa
-~~~
-```
-.
-aaa
-~~~
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1688
-
-.
-~~~
-aaa
-```
-~~~
-.
-aaa
-```
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1702
-
-.
-````
-aaa
-```
-``````
-.
-aaa
-```
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1714
-
-.
-~~~~
-aaa
-~~~
-~~~~
-.
-aaa
-~~~
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1729
-
-.
-```
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1736
-
-.
-`````
-
-```
-aaa
-.
-
-```
-aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1749
-
-.
-> ```
-> aaa
-
-bbb
-.
-
-aaa
-
-
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1765
-
-.
-```
-
-
-```
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1779
-
-.
-```
-```
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1791
-
-.
- ```
- aaa
-aaa
-```
-.
-aaa
-aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1803
-
-.
- ```
-aaa
- aaa
-aaa
- ```
-.
-aaa
-aaa
-aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1817
-
-.
- ```
- aaa
- aaa
- aaa
- ```
-.
-aaa
- aaa
-aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1833
-
-.
- ```
- aaa
- ```
-.
-```
-aaa
-```
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1848
-
-.
-```
-aaa
- ```
-.
-aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1858
-
-.
- ```
-aaa
- ```
-.
-aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1870
-
-.
-```
-aaa
- ```
-.
-aaa
- ```
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1884
-
-.
-``` ```
-aaa
-.
-
-aaa
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1893
-
-.
-~~~~~~
-aaa
-~~~ ~~
-.
-aaa
-~~~ ~~
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1907
-
-.
-foo
-```
-bar
-```
-baz
-.
-foo
-bar
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1924
-
-.
-foo
----
-~~~
-bar
-~~~
-# baz
-.
-foo
-bar
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1946
-
-.
-```ruby
-def foo(x)
- return 3
-end
-```
-.
-def foo(x)
- return 3
-end
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1960
-
-.
-~~~~ ruby startline=3 $%@#$
-def foo(x)
- return 3
-end
-~~~~~~~
-.
-def foo(x)
- return 3
-end
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1974
-
-.
-````;
-````
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1984
-
-.
-``` aa ```
-foo
-.
-aa
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 1995
-
-.
-~~~ aa ``` ~~~
-foo
-~~~
-.
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2007
-
-.
-```
-``` aaa
-```
-.
-``` aaa
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2086
-
-.
-
-
-**Hello**,
-
-_world_.
-
- |
-.
-
-
-**Hello**,
-world.
-
- |
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2115
-
-.
-
-
-okay.
-.
-
-okay.
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2137
-
-.
-
-*foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2161
-
-.
-
-
-*Markdown*
-
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2177
-
-.
-
-
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2188
-
-.
-
-
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2200
-
-.
-
-*foo*
-
-*bar*
-.
-
-*foo*
-
bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2216
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2256
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2273
-
-.
-
-``` c
-int x = 33;
-```
-.
-
-``` c
-int x = 33;
-```
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2290
-
-.
-
-*bar*
-
-.
-
-*bar*
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2303
-
-.
-
-*bar*
-
-.
-
-*bar*
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2314
-
-.
-
-*bar*
-
-.
-
-*bar*
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2325
-
-.
-
-*bar*
-.
-
-*bar*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2340
-
-.
-
-*foo*
-
-.
-
-*foo*
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2355
-
-.
-
-
-*foo*
-
-
-.
-
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2373
-
-.
-
*foo*
-.
-
foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2389
-
-.
-
-import Text.HTML.TagSoup
-
-main :: IO ()
-main = print $ parseTags tags
-
-okay
-.
-
-import Text.HTML.TagSoup
-
-main :: IO ()
-main = print $ parseTags tags
-
-
okay
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2410
-
-.
-
-okay
-.
-
-
okay
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2429
-
-.
-
-okay
-.
-
-
okay
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2452
-
-.
-
-*foo*
-.
-
-
foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2503
-
-.
-*bar*
-*baz*
-.
-*bar*
-
baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2515
-
-.
-1. *bar*
-.
-1. *bar*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2528
-
-.
-
-okay
-.
-
-
okay
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2546
-
-.
-';
-
-?>
-okay
-.
-';
-
-?>
-
okay
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2565
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2574
-
-.
-
-okay
-.
-
-
okay
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2607
-
-.
-
-
-
-.
-
-
<!-- foo -->
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2618
-
-.
-
-
-
-.
-
-
<div>
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2632
-
-.
-Foo
-
-bar
-
-.
-
Foo
-
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2649
-
-.
-
-bar
-
-*foo*
-.
-
-bar
-
-*foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2664
-
-.
-Foo
-
-baz
-.
-Foo
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2705
-
-.
-
-
-*Emphasized* text.
-
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2718
-
-.
-
-*Emphasized* text.
-
-.
-
-*Emphasized* text.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2740
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2767
-
-.
-
-.
-
-
-<td>
- Hi
-</td>
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2815
-
-.
-[foo]: /url "title"
-
-[foo]
-.
-
foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2824
-
-.
- [foo]:
- /url
- 'the title'
-
-[foo]
-.
-
foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2835
-
-.
-[Foo*bar\]]:my_(url) 'title (with parens)'
-
-[Foo*bar\]]
-.
-
Foo*bar]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2844
-
-.
-[Foo bar]:
-
-'title'
-
-[Foo bar]
-.
-Foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2857
-
-.
-[foo]: /url '
-title
-line1
-line2
-'
-
-[foo]
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2876
-
-.
-[foo]: /url 'title
-
-with blank line'
-
-[foo]
-.
-[foo]: /url 'title
-with blank line'
-[foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2891
-
-.
-[foo]:
-/url
-
-[foo]
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2903
-
-.
-[foo]:
-
-[foo]
-.
-[foo]:
-[foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2915
-
-.
-[foo]: <>
-
-[foo]
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2926
-
-.
-[foo]: (baz)
-
-[foo]
-.
-[foo]: (baz)
-[foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2939
-
-.
-[foo]: /url\bar\*baz "foo\"bar\baz"
-
-[foo]
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2950
-
-.
-[foo]
-
-[foo]: url
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2962
-
-.
-[foo]
-
-[foo]: first
-[foo]: second
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2975
-
-.
-[FOO]: /url
-
-[Foo]
-.
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2984
-
-.
-[ΑΓΩ]: /φου
-
-[αγω]
-.
-αγω
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 2996
-
-.
-[foo]: /url
-.
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3004
-
-.
-[
-foo
-]: /url
-bar
-.
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3017
-
-.
-[foo]: /url "title" ok
-.
-[foo]: /url "title" ok
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3026
-
-.
-[foo]: /url
-"title" ok
-.
-"title" ok
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3037
-
-.
- [foo]: /url "title"
-
-[foo]
-.
-[foo]: /url "title"
-
-[foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3051
-
-.
-```
-[foo]: /url
-```
-
-[foo]
-.
-[foo]: /url
-
-[foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3066
-
-.
-Foo
-[bar]: /baz
-
-[bar]
-.
-Foo
-[bar]: /baz
-[bar]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3081
-
-.
-# [Foo]
-[foo]: /url
-> bar
-.
-
-
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3092
-
-.
-[foo]: /url
-bar
-===
-[foo]
-.
-bar
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3102
-
-.
-[foo]: /url
-===
-[foo]
-.
-===
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3115
-
-.
-[foo]: /foo-url "foo"
-[bar]: /bar-url
- "bar"
-[baz]: /baz-url
-
-[foo],
-[bar],
-[baz]
-.
-foo,
-bar,
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3136
-
-.
-[foo]
-
-> [foo]: /url
-.
-foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3153
-
-.
-[foo]: /url
-.
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3170
-
-.
-aaa
-
-bbb
-.
-aaa
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3182
-
-.
-aaa
-bbb
-
-ccc
-ddd
-.
-aaa
-bbb
-ccc
-ddd
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3198
-
-.
-aaa
-
-
-bbb
-.
-aaa
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3211
-
-.
- aaa
- bbb
-.
-aaa
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3223
-
-.
-aaa
- bbb
- ccc
-.
-aaa
-bbb
-ccc
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3237
-
-.
- aaa
-bbb
-.
-aaa
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3246
-
-.
- aaa
-bbb
-.
-aaa
-
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3260
-
-.
-aaa
-bbb
-.
-aaa
-bbb
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3277
-
-.
-
-
-aaa
-
-
-# aaa
-
-
-.
-aaa
-aaa
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3343
-
-.
-> # Foo
-> bar
-> baz
-.
-
-Foo
-bar
-baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3358
-
-.
-># Foo
->bar
-> baz
-.
-
-Foo
-bar
-baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3373
-
-.
- > # Foo
- > bar
- > baz
-.
-
-Foo
-bar
-baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3388
-
-.
- > # Foo
- > bar
- > baz
-.
-> # Foo
-> bar
-> baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3403
-
-.
-> # Foo
-> bar
-baz
-.
-
-Foo
-bar
-baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3419
-
-.
-> bar
-baz
-> foo
-.
-
-bar
-baz
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3443
-
-.
-> foo
----
-.
-
-foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3463
-
-.
-> - foo
-- bar
-.
-
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3481
-
-.
-> foo
- bar
-.
-
-foo
-
-
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3494
-
-.
-> ```
-foo
-```
-.
-
-
-
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3510
-
-.
-> foo
- - bar
-.
-
-foo
-- bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3534
-
-.
->
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3542
-
-.
->
->
->
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3554
-
-.
->
-> foo
->
-.
-
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3567
-
-.
-> foo
-
-> bar
-.
-
-foo
-
-
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3589
-
-.
-> foo
-> bar
-.
-
-foo
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3602
-
-.
-> foo
->
-> bar
-.
-
-foo
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3616
-
-.
-foo
-> bar
-.
-foo
-
-bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3630
-
-.
-> aaa
-***
-> bbb
-.
-
-aaa
-
-
-
-bbb
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3648
-
-.
-> bar
-baz
-.
-
-bar
-baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3659
-
-.
-> bar
-
-baz
-.
-
-bar
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3671
-
-.
-> bar
->
-baz
-.
-
-bar
-
-baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3687
-
-.
-> > > foo
-bar
-.
-
-
-
-foo
-bar
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3702
-
-.
->>> foo
-> bar
->>baz
-.
-
-
-
-foo
-bar
-baz
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3724
-
-.
-> code
-
-> not code
-.
-
-code
-
-
-
-not code
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3778
-
-.
-A paragraph
-with two lines.
-
- indented code
-
-> A block quote.
-.
-A paragraph
-with two lines.
-indented code
-
-
-A block quote.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3800
-
-.
-1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-
--
-
A paragraph
-with two lines.
-indented code
-
-
-A block quote.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3833
-
-.
-- one
-
- two
-.
-
-two
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3845
-
-.
-- one
-
- two
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3859
-
-.
- - one
-
- two
-.
-
- two
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3872
-
-.
- - one
-
- two
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3894
-
-.
- > > 1. one
->>
->> two
-.
-
-
-
--
-
one
-two
-
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3921
-
-.
->>- one
->>
- > > two
-.
-
-
-
-two
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3940
-
-.
--one
-
-2.two
-.
--one
-2.two
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3953
-
-.
-- foo
-
-
- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3970
-
-.
-1. foo
-
- ```
- bar
- ```
-
- baz
-
- > bam
-.
-
--
-
foo
-bar
-
-baz
-
-bam
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 3998
-
-.
-- Foo
-
- bar
-
-
- baz
-.
-
--
-
Foo
-bar
-
-
-baz
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4020
-
-.
-123456789. ok
-.
-
-- ok
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4029
-
-.
-1234567890. not ok
-.
-1234567890. not ok
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4038
-
-.
-0. ok
-.
-
-- ok
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4047
-
-.
-003. ok
-.
-
-- ok
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4058
-
-.
--1. not ok
-.
--1. not ok
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4081
-
-.
-- foo
-
- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4098
-
-.
- 10. foo
-
- bar
-.
-
--
-
foo
-bar
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4117
-
-.
- indented code
-
-paragraph
-
- more code
-.
-indented code
-
-paragraph
-more code
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4132
-
-.
-1. indented code
-
- paragraph
-
- more code
-.
-
--
-
indented code
-
-paragraph
-more code
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4154
-
-.
-1. indented code
-
- paragraph
-
- more code
-.
-
--
-
indented code
-
-paragraph
-more code
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4181
-
-.
- foo
-
-bar
-.
-foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4191
-
-.
-- foo
-
- bar
-.
-
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4208
-
-.
-- foo
-
- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4236
-
-.
--
- foo
--
- ```
- bar
- ```
--
- baz
-.
-
-- foo
--
-
bar
-
-
--
-
baz
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4262
-
-.
--
- foo
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4276
-
-.
--
-
- foo
-.
-
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4290
-
-.
-- foo
--
-- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4305
-
-.
-- foo
--
-- bar
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4320
-
-.
-1. foo
-2.
-3. bar
-.
-
-- foo
-
-- bar
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4335
-
-.
-*
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4345
-
-.
-foo
-*
-
-foo
-1.
-.
-foo
-*
-foo
-1.
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4367
-
-.
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-
--
-
A paragraph
-with two lines.
-indented code
-
-
-A block quote.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4391
-
-.
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-
--
-
A paragraph
-with two lines.
-indented code
-
-
-A block quote.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4415
-
-.
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-
--
-
A paragraph
-with two lines.
-indented code
-
-
-A block quote.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4439
-
-.
- 1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-.
-1. A paragraph
- with two lines.
-
- indented code
-
- > A block quote.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4469
-
-.
- 1. A paragraph
-with two lines.
-
- indented code
-
- > A block quote.
-.
-
--
-
A paragraph
-with two lines.
-indented code
-
-
-A block quote.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4493
-
-.
- 1. A paragraph
- with two lines.
-.
-
-- A paragraph
-with two lines.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4506
-
-.
-> 1. > Blockquote
-continued here.
-.
-
-
--
-
-Blockquote
-continued here.
-
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4523
-
-.
-> 1. > Blockquote
-> continued here.
-.
-
-
--
-
-Blockquote
-continued here.
-
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4551
-
-.
-- foo
- - bar
- - baz
- - boo
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4577
-
-.
-- foo
- - bar
- - baz
- - boo
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4594
-
-.
-10) foo
- - bar
-.
-
-- foo
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4610
-
-.
-10) foo
- - bar
-.
-
-- foo
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4625
-
-.
-- - foo
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4638
-
-.
-1. - 2. foo
-.
-
--
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4657
-
-.
-- # Foo
-- Bar
- ---
- baz
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4893
-
-.
-- foo
-- bar
-+ baz
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4908
-
-.
-1. foo
-2. bar
-3) baz
-.
-
-- foo
-- bar
-
-
-- baz
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 4927
-
-.
-Foo
-- bar
-- baz
-.
-Foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5004
-
-.
-The number of windows in my house is
-14. The number of doors is 6.
-.
-The number of windows in my house is
-14. The number of doors is 6.
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5014
-
-.
-The number of windows in my house is
-1. The number of doors is 6.
-.
-The number of windows in my house is
-
-- The number of doors is 6.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5028
-
-.
-- foo
-
-- bar
-
-
-- baz
-.
-
--
-
foo
-
--
-
bar
-
--
-
baz
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5049
-
-.
-- foo
- - bar
- - baz
-
-
- bim
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5079
-
-.
-- foo
-- bar
-
-
-
-- baz
-- bim
-.
-
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5100
-
-.
-- foo
-
- notcode
-
-- foo
-
-
-
- code
-.
-
--
-
foo
-notcode
-
--
-
foo
-
-
-
-code
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5131
-
-.
-- a
- - b
- - c
- - d
- - e
- - f
-- g
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5152
-
-.
-1. a
-
- 2. b
-
- 3. c
-.
-
--
-
a
-
--
-
b
-
--
-
c
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5176
-
-.
-- a
- - b
- - c
- - d
- - e
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5196
-
-.
-1. a
-
- 2. b
-
- 3. c
-.
-
--
-
a
-
--
-
b
-
-
-3. c
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5219
-
-.
-- a
-- b
-
-- c
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5241
-
-.
-* a
-*
-
-* c
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5263
-
-.
-- a
-- b
-
- c
-- d
-.
-
--
-
a
-
--
-
b
-c
-
--
-
d
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5285
-
-.
-- a
-- b
-
- [ref]: /url
-- d
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5308
-
-.
-- a
-- ```
- b
-
-
- ```
-- c
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5334
-
-.
-- a
- - b
-
- c
-- d
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5358
-
-.
-* a
- > b
- >
-* c
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5378
-
-.
-- a
- > b
- ```
- c
- ```
-- d
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5401
-
-.
-- a
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5410
-
-.
-- a
- - b
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5427
-
-.
-1. ```
- foo
- ```
-
- bar
-.
-
--
-
foo
-
-bar
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5446
-
-.
-* foo
- * bar
-
- baz
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5464
-
-.
-- a
- - b
- - c
-
-- d
- - e
- - f
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5498
-
-.
-`hi`lo`
-.
-hilo`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5512
-
-.
-\!\"\#\$\%\&\'\(\)\*\+\,\-\.\/\:\;\<\=\>\?\@\[\\\]\^\_\`\{\|\}\~
-.
-!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5522
-
-.
-\ \A\a\ \3\φ\«
-.
-\ \A\a\ \3\φ\«
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5532
-
-.
-\*not emphasized*
-\
not a tag
-\[not a link](/foo)
-\`not code`
-1\. not a list
-\* not a list
-\# not a heading
-\[foo]: /url "not a reference"
-\ö not a character entity
-.
-*not emphasized*
-<br/> not a tag
-[not a link](/foo)
-`not code`
-1. not a list
-* not a list
-# not a heading
-[foo]: /url "not a reference"
-ö not a character entity
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5557
-
-.
-\\*emphasis*
-.
-\emphasis
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5566
-
-.
-foo\
-bar
-.
-foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5578
-
-.
-`` \[\` ``
-.
-\[\`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5585
-
-.
- \[\]
-.
-\[\]
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5593
-
-.
-~~~
-\[\]
-~~~
-.
-\[\]
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5603
-
-.
-
-.
-http://example.com?find=\*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5610
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5620
-
-.
-[foo](/bar\* "ti\*tle")
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5627
-
-.
-[foo]
-
-[foo]: /bar\* "ti\*tle"
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5636
-
-.
-``` foo\+bar
-foo
-```
-.
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5673
-
-.
- & © Æ Ď
-¾ ℋ ⅆ
-∲ ≧̸
-.
- & © Æ Ď
-¾ ℋ ⅆ
-∲ ≧̸
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5692
-
-.
-# Ӓ Ϡ �
-.
-# Ӓ Ϡ �
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5705
-
-.
-" ആ ಫ
-.
-" ആ ಫ
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5714
-
-.
- &x; &#; &#x;
-�
-&#abcdef0;
-&ThisIsNotDefined; &hi?;
-.
-  &x; &#; &#x;
-�
-&#abcdef0;
-&ThisIsNotDefined; &hi?;
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5731
-
-.
-©
-.
-©
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5741
-
-.
-&MadeUpEntity;
-.
-&MadeUpEntity;
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5752
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5759
-
-.
-[foo](/föö "föö")
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5766
-
-.
-[foo]
-
-[foo]: /föö "föö"
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5775
-
-.
-``` föö
-foo
-```
-.
-foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5788
-
-.
-`föö`
-.
-föö
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5795
-
-.
- föfö
-.
-föfö
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5807
-
-.
-*foo*
-*foo*
-.
-*foo*
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5815
-
-.
-* foo
-
-* foo
-.
-* foo
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5826
-
-.
-foo
bar
-.
-foo
-
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5834
-
-.
- foo
-.
- foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5841
-
-.
-[a](url "tit")
-.
-[a](url "tit")
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5869
-
-.
-`foo`
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5880
-
-.
-`` foo ` bar ``
-.
-foo ` bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5890
-
-.
-` `` `
-.
-``
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5898
-
-.
-` `` `
-.
- ``
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5907
-
-.
-` a`
-.
- a
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5916
-
-.
-` b `
-.
- b
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5924
-
-.
-` `
-` `
-.
-
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5935
-
-.
-``
-foo
-bar
-baz
-``
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5945
-
-.
-``
-foo
-``
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5956
-
-.
-`foo bar
-baz`
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5973
-
-.
-`foo\`bar`
-.
-foo\bar`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5984
-
-.
-``foo`bar``
-.
-foo`bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 5990
-
-.
-` foo `` bar `
-.
-foo `` bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6002
-
-.
-*foo`*`
-.
-*foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6011
-
-.
-[not a `link](/foo`)
-.
-[not a link](/foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6021
-
-.
-``
-.
-<a href="">`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6030
-
-.
-`
-.
-`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6039
-
-.
-``
-.
-<http://foo.bar.baz>`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6048
-
-.
-`
-.
-http://foo.bar.`baz`
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6058
-
-.
-```foo``
-.
-```foo``
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6065
-
-.
-`foo
-.
-`foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6074
-
-.
-`foo``bar``
-.
-`foobar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6291
-
-.
-*foo bar*
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6301
-
-.
-a * foo bar*
-.
-a * foo bar*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6312
-
-.
-a*"foo"*
-.
-a*"foo"*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6321
-
-.
-* a *
-.
-* a *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6330
-
-.
-foo*bar*
-.
-foobar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6337
-
-.
-5*6*78
-.
-5678
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6346
-
-.
-_foo bar_
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6356
-
-.
-_ foo bar_
-.
-_ foo bar_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6366
-
-.
-a_"foo"_
-.
-a_"foo"_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6375
-
-.
-foo_bar_
-.
-foo_bar_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6382
-
-.
-5_6_78
-.
-5_6_78
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6389
-
-.
-пристаням_стремятся_
-.
-пристаням_стремятся_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6399
-
-.
-aa_"bb"_cc
-.
-aa_"bb"_cc
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6410
-
-.
-foo-_(bar)_
-.
-foo-(bar)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6422
-
-.
-_foo*
-.
-_foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6432
-
-.
-*foo bar *
-.
-*foo bar *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6441
-
-.
-*foo bar
-*
-.
-*foo bar
-*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6454
-
-.
-*(*foo)
-.
-*(*foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6464
-
-.
-*(*foo*)*
-.
-(foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6473
-
-.
-*foo*bar
-.
-foobar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6486
-
-.
-_foo bar _
-.
-_foo bar _
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6496
-
-.
-_(_foo)
-.
-_(_foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6505
-
-.
-_(_foo_)_
-.
-(foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6514
-
-.
-_foo_bar
-.
-_foo_bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6521
-
-.
-_пристаням_стремятся
-.
-_пристаням_стремятся
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6528
-
-.
-_foo_bar_baz_
-.
-foo_bar_baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6539
-
-.
-_(bar)_.
-.
-(bar).
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6548
-
-.
-**foo bar**
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6558
-
-.
-** foo bar**
-.
-** foo bar**
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6569
-
-.
-a**"foo"**
-.
-a**"foo"**
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6578
-
-.
-foo**bar**
-.
-foobar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6587
-
-.
-__foo bar__
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6597
-
-.
-__ foo bar__
-.
-__ foo bar__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6605
-
-.
-__
-foo bar__
-.
-__
-foo bar__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6617
-
-.
-a__"foo"__
-.
-a__"foo"__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6626
-
-.
-foo__bar__
-.
-foo__bar__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6633
-
-.
-5__6__78
-.
-5__6__78
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6640
-
-.
-пристаням__стремятся__
-.
-пристаням__стремятся__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6647
-
-.
-__foo, __bar__, baz__
-.
-foo, bar, baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6658
-
-.
-foo-__(bar)__
-.
-foo-(bar)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6671
-
-.
-**foo bar **
-.
-**foo bar **
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6684
-
-.
-**(**foo)
-.
-**(**foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6694
-
-.
-*(**foo**)*
-.
-(foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6701
-
-.
-**Gomphocarpus (*Gomphocarpus physocarpus*, syn.
-*Asclepias physocarpa*)**
-.
-Gomphocarpus (Gomphocarpus physocarpus, syn.
-Asclepias physocarpa)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6710
-
-.
-**foo "*bar*" foo**
-.
-foo "bar" foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6719
-
-.
-**foo**bar
-.
-foobar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6731
-
-.
-__foo bar __
-.
-__foo bar __
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6741
-
-.
-__(__foo)
-.
-__(__foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6751
-
-.
-_(__foo__)_
-.
-(foo)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6760
-
-.
-__foo__bar
-.
-__foo__bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6767
-
-.
-__пристаням__стремятся
-.
-__пристаням__стремятся
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6774
-
-.
-__foo__bar__baz__
-.
-foo__bar__baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6785
-
-.
-__(bar)__.
-.
-(bar).
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6797
-
-.
-*foo [bar](/url)*
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6804
-
-.
-*foo
-bar*
-.
-foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6816
-
-.
-_foo __bar__ baz_
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6823
-
-.
-_foo _bar_ baz_
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6830
-
-.
-__foo_ bar_
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6837
-
-.
-*foo *bar**
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6844
-
-.
-*foo **bar** baz*
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6850
-
-.
-*foo**bar**baz*
-.
-foobarbaz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6874
-
-.
-*foo**bar*
-.
-foo**bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6887
-
-.
-***foo** bar*
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6894
-
-.
-*foo **bar***
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6901
-
-.
-*foo**bar***
-.
-foobar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6912
-
-.
-foo***bar***baz
-.
-foobarbaz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6918
-
-.
-foo******bar*********baz
-.
-foobar***baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6927
-
-.
-*foo **bar *baz* bim** bop*
-.
-foo bar baz bim bop
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6934
-
-.
-*foo [*bar*](/url)*
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6943
-
-.
-** is not an empty emphasis
-.
-** is not an empty emphasis
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6950
-
-.
-**** is not an empty strong emphasis
-.
-**** is not an empty strong emphasis
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6963
-
-.
-**foo [bar](/url)**
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6970
-
-.
-**foo
-bar**
-.
-foo
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6982
-
-.
-__foo _bar_ baz__
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6989
-
-.
-__foo __bar__ baz__
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 6996
-
-.
-____foo__ bar__
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7003
-
-.
-**foo **bar****
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7010
-
-.
-**foo *bar* baz**
-.
-foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7017
-
-.
-**foo*bar*baz**
-.
-foobarbaz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7024
-
-.
-***foo* bar**
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7031
-
-.
-**foo *bar***
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7040
-
-.
-**foo *bar **baz**
-bim* bop**
-.
-foo bar baz
-bim bop
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7049
-
-.
-**foo [*bar*](/url)**
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7058
-
-.
-__ is not an empty emphasis
-.
-__ is not an empty emphasis
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7065
-
-.
-____ is not an empty strong emphasis
-.
-____ is not an empty strong emphasis
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7075
-
-.
-foo ***
-.
-foo ***
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7082
-
-.
-foo *\**
-.
-foo *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7089
-
-.
-foo *_*
-.
-foo _
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7096
-
-.
-foo *****
-.
-foo *****
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7103
-
-.
-foo **\***
-.
-foo *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7110
-
-.
-foo **_**
-.
-foo _
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7121
-
-.
-**foo*
-.
-*foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7128
-
-.
-*foo**
-.
-foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7135
-
-.
-***foo**
-.
-*foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7142
-
-.
-****foo*
-.
-***foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7149
-
-.
-**foo***
-.
-foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7156
-
-.
-*foo****
-.
-foo***
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7166
-
-.
-foo ___
-.
-foo ___
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7173
-
-.
-foo _\__
-.
-foo _
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7180
-
-.
-foo _*_
-.
-foo *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7187
-
-.
-foo _____
-.
-foo _____
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7194
-
-.
-foo __\___
-.
-foo _
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7201
-
-.
-foo __*__
-.
-foo *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7208
-
-.
-__foo_
-.
-_foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7219
-
-.
-_foo__
-.
-foo_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7226
-
-.
-___foo__
-.
-_foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7233
-
-.
-____foo_
-.
-___foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7240
-
-.
-__foo___
-.
-foo_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7247
-
-.
-_foo____
-.
-foo___
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7257
-
-.
-**foo**
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7264
-
-.
-*_foo_*
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7271
-
-.
-__foo__
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7278
-
-.
-_*foo*_
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7288
-
-.
-****foo****
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7295
-
-.
-____foo____
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7306
-
-.
-******foo******
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7315
-
-.
-***foo***
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7322
-
-.
-_____foo_____
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7331
-
-.
-*foo _bar* baz_
-.
-foo _bar baz_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7338
-
-.
-*foo __bar *baz bim__ bam*
-.
-foo bar *baz bim bam
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7347
-
-.
-**foo **bar baz**
-.
-**foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7354
-
-.
-*foo *bar baz*
-.
-*foo bar baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7363
-
-.
-*[bar*](/url)
-.
-*bar*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7370
-
-.
-_foo [bar_](/url)
-.
-_foo bar_
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7377
-
-.
-*
-.
-*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7384
-
-.
-**
-.
-**
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7391
-
-.
-__
-.
-__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7398
-
-.
-*a `*`*
-.
-a *
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7405
-
-.
-_a `_`_
-.
-a _
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7412
-
-.
-**a
-.
-**ahttp://foo.bar/?q=**
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7419
-
-.
-__a
-.
-__ahttp://foo.bar/?q=__
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7502
-
-.
-[link](/uri "title")
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7511
-
-.
-[link](/uri)
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7520
-
-.
-[link]()
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7527
-
-.
-[link](<>)
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7536
-
-.
-[link](/my uri)
-.
-[link](/my uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7542
-
-.
-[link]()
-.
-
link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7551
-
-.
-[link](foo
-bar)
-.
-
[link](foo
-bar)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7559
-
-.
-[link](
)
-.
-[link]()
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7570
-
-.
-[a]()
-.
-a
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7578
-
-.
-[link]()
-.
-[link](<foo>)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7587
-
-.
-[a](
-[a](c)
-.
-[a](<b)c
-[a](<b)c>
-[a](c)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7599
-
-.
-[link](\(foo\))
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7608
-
-.
-[link](foo(and(bar)))
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7617
-
-.
-[link](foo\(and\(bar\))
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7624
-
-.
-[link]()
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7634
-
-.
-[link](foo\)\:)
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7643
-
-.
-[link](#fragment)
-
-[link](http://example.com#fragment)
-
-[link](http://example.com?foo=3#frag)
-.
-link
-link
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7659
-
-.
-[link](foo\bar)
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7675
-
-.
-[link](foo%20bä)
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7686
-
-.
-[link]("title")
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7695
-
-.
-[link](/url "title")
-[link](/url 'title')
-[link](/url (title))
-.
-link
-link
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7709
-
-.
-[link](/url "title \""")
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7719
-
-.
-[link](/url "title")
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7728
-
-.
-[link](/url "title "and" title")
-.
-[link](/url "title "and" title")
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7737
-
-.
-[link](/url 'title "and" title')
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7761
-
-.
-[link]( /uri
- "title" )
-.
-link
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7772
-
-.
-[link] (/uri)
-.
-[link] (/uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7782
-
-.
-[link [foo [bar]]](/uri)
-.
-link [foo [bar]]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7789
-
-.
-[link] bar](/uri)
-.
-[link] bar](/uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7796
-
-.
-[link [bar](/uri)
-.
-[link bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7803
-
-.
-[link \[bar](/uri)
-.
-link [bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7812
-
-.
-[link *foo **bar** `#`*](/uri)
-.
-link foo bar #
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7819
-
-.
-[](/uri)
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7828
-
-.
-[foo [bar](/uri)](/uri)
-.
-[foo bar](/uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7835
-
-.
-[foo *[bar [baz](/uri)](/uri)*](/uri)
-.
-[foo [bar baz](/uri)](/uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7842
-
-.
-](uri2)](uri3)
-.
-](http://github.com/uri3)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7852
-
-.
-*[foo*](/uri)
-.
-*foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7859
-
-.
-[foo *bar](baz*)
-.
-foo *bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7869
-
-.
-*foo [bar* baz]
-.
-foo [bar baz]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7879
-
-.
-[foo
-.
-[foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7886
-
-.
-[foo`](/uri)`
-.
-[foo](/uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7893
-
-.
-[foo
-.
-[foohttp://example.com/?search=](uri)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7931
-
-.
-[foo][bar]
-
-[bar]: /url "title"
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7946
-
-.
-[link [foo [bar]]][ref]
-
-[ref]: /uri
-.
-link [foo [bar]]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7955
-
-.
-[link \[bar][ref]
-
-[ref]: /uri
-.
-link [bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7966
-
-.
-[link *foo **bar** `#`*][ref]
-
-[ref]: /uri
-.
-link foo bar #
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7975
-
-.
-[][ref]
-
-[ref]: /uri
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7986
-
-.
-[foo [bar](/uri)][ref]
-
-[ref]: /uri
-.
-[foo bar]ref
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 7995
-
-.
-[foo *bar [baz][ref]*][ref]
-
-[ref]: /uri
-.
-[foo bar baz]ref
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8010
-
-.
-*[foo*][ref]
-
-[ref]: /uri
-.
-*foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8019
-
-.
-[foo *bar][ref]
-
-[ref]: /uri
-.
-foo *bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8031
-
-.
-[foo
-
-[ref]: /uri
-.
-[foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8040
-
-.
-[foo`][ref]`
-
-[ref]: /uri
-.
-[foo][ref]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8049
-
-.
-[foo
-
-[ref]: /uri
-.
-[foohttp://example.com/?search=][ref]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8060
-
-.
-[foo][BaR]
-
-[bar]: /url "title"
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8071
-
-.
-[Толпой][Толпой] is a Russian word.
-
-[ТОЛПОЙ]: /url
-.
-Толпой is a Russian word.
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8083
-
-.
-[Foo
- bar]: /url
-
-[Baz][Foo bar]
-.
-Baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8096
-
-.
-[foo] [bar]
-
-[bar]: /url "title"
-.
-[foo] bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8105
-
-.
-[foo]
-[bar]
-
-[bar]: /url "title"
-.
-[foo]
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8146
-
-.
-[foo]: /url1
-
-[foo]: /url2
-
-[bar][foo]
-.
-bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8161
-
-.
-[bar][foo\!]
-
-[foo!]: /url
-.
-[bar][foo!]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8173
-
-.
-[foo][ref[]
-
-[ref[]: /uri
-.
-[foo][ref[]
-[ref[]: /uri
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8183
-
-.
-[foo][ref[bar]]
-
-[ref[bar]]: /uri
-.
-[foo][ref[bar]]
-[ref[bar]]: /uri
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8193
-
-.
-[[[foo]]]
-
-[[[foo]]]: /url
-.
-[[[foo]]]
-[[[foo]]]: /url
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8203
-
-.
-[foo][ref\[]
-
-[ref\[]: /uri
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8214
-
-.
-[bar\\]: /uri
-
-[bar\\]
-.
-bar\
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8225
-
-.
-[]
-
-[]: /uri
-.
-[]
-[]: /uri
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8235
-
-.
-[
- ]
-
-[
- ]: /uri
-.
-[
-]
-[
-]: /uri
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8258
-
-.
-[foo][]
-
-[foo]: /url "title"
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8267
-
-.
-[*foo* bar][]
-
-[*foo* bar]: /url "title"
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8278
-
-.
-[Foo][]
-
-[foo]: /url "title"
-.
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8291
-
-.
-[foo]
-[]
-
-[foo]: /url "title"
-.
-foo
-[]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8311
-
-.
-[foo]
-
-[foo]: /url "title"
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8320
-
-.
-[*foo* bar]
-
-[*foo* bar]: /url "title"
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8329
-
-.
-[[*foo* bar]]
-
-[*foo* bar]: /url "title"
-.
-[foo bar]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8338
-
-.
-[[bar [foo]
-
-[foo]: /url
-.
-[[bar foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8349
-
-.
-[Foo]
-
-[foo]: /url "title"
-.
-Foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8360
-
-.
-[foo] bar
-
-[foo]: /url
-.
-foo bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8372
-
-.
-\[foo]
-
-[foo]: /url "title"
-.
-[foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8384
-
-.
-[foo*]: /url
-
-*[foo*]
-.
-*foo*
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8396
-
-.
-[foo][bar]
-
-[foo]: /url1
-[bar]: /url2
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8405
-
-.
-[foo][]
-
-[foo]: /url1
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8415
-
-.
-[foo]()
-
-[foo]: /url1
-.
-foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8423
-
-.
-[foo](not a link)
-
-[foo]: /url1
-.
-foo(not a link)
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8434
-
-.
-[foo][bar][baz]
-
-[baz]: /url
-.
-[foo]bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8446
-
-.
-[foo][bar][baz]
-
-[baz]: /url1
-[bar]: /url2
-.
-foobaz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8459
-
-.
-[foo][bar][baz]
-
-[baz]: /url1
-[foo]: /url2
-.
-[foo]bar
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8482
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8489
-
-.
-![foo *bar*]
-
-[foo *bar*]: train.jpg "train & tracks"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8498
-
-.
-](/url2)
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8505
-
-.
-](/url2)
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8519
-
-.
-![foo *bar*][]
-
-[foo *bar*]: train.jpg "train & tracks"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8528
-
-.
-![foo *bar*][foobar]
-
-[FOOBAR]: train.jpg "train & tracks"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8537
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8544
-
-.
-My 
-.
-My 
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8551
-
-.
-![foo]()
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8558
-
-.
-
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8567
-
-.
-![foo][bar]
-
-[bar]: /url
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8576
-
-.
-![foo][bar]
-
-[BAR]: /url
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8587
-
-.
-![foo][]
-
-[foo]: /url "title"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8596
-
-.
-![*foo* bar][]
-
-[*foo* bar]: /url "title"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8607
-
-.
-![Foo][]
-
-[foo]: /url "title"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8619
-
-.
-![foo]
-[]
-
-[foo]: /url "title"
-.
-
-[]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8632
-
-.
-![foo]
-
-[foo]: /url "title"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8641
-
-.
-![*foo* bar]
-
-[*foo* bar]: /url "title"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8652
-
-.
-![[foo]]
-
-[[foo]]: /url "title"
-.
-![[foo]]
-[[foo]]: /url "title"
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8664
-
-.
-![Foo]
-
-[foo]: /url "title"
-.
-
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8676
-
-.
-!\[foo]
-
-[foo]: /url "title"
-.
-![foo]
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8688
-
-.
-\![foo]
-
-[foo]: /url "title"
-.
-!foo
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8721
-
-.
-
-.
-http://foo.bar.baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8728
-
-.
-
-.
-http://foo.bar.baz/test?q=hello&id=22&boolean
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8735
-
-.
-
-.
-irc://foo.bar:2233/baz
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8744
-
-.
-
-.
-MAILTO:FOO@BAR.BAZ
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8756
-
-.
-
-.
-a+b+c:d
-.
-
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-src line: 8763
-
-.
-
-.
-![\"moon\"](\"moon.jpg\")
![\"foo](\"train.jpg\" "\\"train")
![\"foo](\"/path/to/train.jpg\" "\\"title\\"")