xyz
xyz
xyz
xyz
hi
hi
hi
bar
```````````````````````````````` ```````````````````````````````` example {#foo .special} # Hi .hi
```````````````````````````````` **Consecutive attribute specifiers may be used, either for blocks or for inlines.** ```````````````````````````````` example *hi*{.underline}{#foo} .hi
```````````````````````````````` ```````````````````````````````` example {.special} {#foo} * * * * .Hi
```````````````````````````````` Numerical suffixes will be added to avoid duplicate identifiers: ```````````````````````````````` example # Hi # Hi # Hi .Visit www.commonmark.org/help for more information.
```````````````````````````````` We then apply [extended autolink path validation](@) as follows: Trailing punctuation (specifically, `?`, `!`, `.`, `,`, `:`, `*`, `_`, and `~`) will not be considered part of the autolink, though they may be included in the interior of the link: ```````````````````````````````` example Visit www.commonmark.org. Visit www.commonmark.org/a.b. Visit www.commonmark.org/~jm/foo/bar.pdf. .Visit www.commonmark.org.
Visit www.commonmark.org/a.b.
Visit www.commonmark.org/~jm/foo/bar.pdf.
```````````````````````````````` When an autolink ends in `)`, we scan the entire autolink for the total number of parentheses. If there is a greater number of closing parentheses than opening ones, we don't consider the last character part of the autolink, in order to facilitate including an autolink inside a parenthesis: ```````````````````````````````` example www.google.com/search?q=Markup+(business) (www.google.com/search?q=Markup+(business)) .www.google.com/search?q=Markup+(business)
(www.google.com/search?q=Markup+(business))
```````````````````````````````` This check is only done when the link ends in a closing parentheses `)`, so if the only parentheses are in the interior of the autolink, no special rules are applied: ```````````````````````````````` example www.google.com/search?q=(business))+ok .www.google.com/search?q=(business))+ok
```````````````````````````````` If an autolink ends in a semicolon (`;`), we check to see if it appears to resemble an [entity reference][entity references]; if the preceding text is `&` followed by one or more alphanumeric characters. If so, it is excluded from the autolink: ```````````````````````````````` example www.google.com/search?q=commonmark&hl=en www.google.com/search?q=commonmark&hl; .www.google.com/search?q=commonmark&hl=en
www.google.com/search?q=commonmark&hl;
```````````````````````````````` `<` immediately ends an autolink. ```````````````````````````````` example www.commonmark.org/he(Visit https://encrypted.google.com/search?q=Markup+(business))
Anonymous FTP is available at ftp://foo.bar.baz.
```````````````````````````````` An [extended email autolink](@) will be recognised when an email address is recognised within any text node. Email addresses are recognised according to the following rules: * One ore more characters which are alphanumeric, or `.`, `-`, `_`, or `+`. * An `@` symbol. * One or more characters which are alphanumeric, or `.`, `-`, or `_`. At least one of the characters here must be a period (`.`). The last character must not be one of `-` or `_`. If the last character is a period (`.`), it will be excluded from the autolink. The scheme `mailto:` will automatically be added to the generated link: ```````````````````````````````` example foo@bar.baz . ```````````````````````````````` `+` can occur before the `@`, but not after. ```````````````````````````````` example hello@mail+xyz.example isn't valid, but hello+xyz@mail.example is. .hello@mail+xyz.example isn't valid, but hello+xyz@mail.example is.
```````````````````````````````` `.`, `-`, and `_` can occur on both sides of the `@`, but only `.` may occur at the end of the email address, in which case it will not be considered part of the address: ```````````````````````````````` example a.b-c_d@a.b a.b-c_d@a.b. a.b-c_d@a.b- a.b-c_d@a.b_ .a.b-c_d@a.b-
a.b-c_d@a.b_
```````````````````````````````` The autolinks extension should not interfere with regular links (#65). ```````````````````````````````` example [a link](http://www.google.com/)stuff? .a linkstuff?
```````````````````````````````` commonmark-extensions-0.2.3.6/test/bracketed_spans.md 0000644 0000000 0000000 00000001117 07346545000 021042 0 ustar 00 0000000 0000000 Bracketed spans work like links with attributes, but without the link destination. ```````````````````````````````` example [foo]{#ident .class key="value value" key2=value2} .foo
```````````````````````````````` ```````````````````````````````` example [foo *bar*]{#ident .class} .foo bar
```````````````````````````````` An attribute is required: ```````````````````````````````` example [foo] .[foo]
```````````````````````````````` commonmark-extensions-0.2.3.6/test/definition_lists.md 0000644 0000000 0000000 00000007261 07346545000 021266 0 ustar 00 0000000 0000000 ## Definition lists The term is given on a line by itself, followed by one or more definitions. Each definition must begin with `:` (after 0-2 spaces); subsequent lines must be indented unless they are lazy paragraph continuations. The list is tight if there is no blank line between the term and the first definition, otherwise loose. ```````````````````````````````` example apple : red fruit orange : orange fruit .red fruit
orange fruit
red fruit
orange fruit
red fruit
contains seeds, crisp, pleasant to taste
orange fruit
{ orange code block }
orange block quote
Para one
Para two
red fruit
computer company
orange fruit
telecom company
red fruit
computer company
orange fruit
telecom company
foo
Foo
😊 A💔 😺
```````````````````````````````` ```````````````````````````````` example :nothing_really: :broken_heart .:nothing_really: :broken_heart
```````````````````````````````` commonmark-extensions-0.2.3.6/test/fancy_lists.md 0000644 0000000 0000000 00000011055 07346545000 020232 0 ustar 00 0000000 0000000 The `fancy_lists` extension allows various styles of ordered lists: With period: ```````````````````````````````` example 1. decimal 2. decimal .B. Russell
I. J. Good
```````````````````````````````` A new list starts with any style change: ```````````````````````````````` example 1. one 2) one .Hi
A block quote.
Hi
A block quote.
Hi
A block quote.
Paragraph text
Hi
::: Hi :::
```````````````````````````````` The closing fence must be at leats as long as the opening fence. ```````````````````````````````` example ::::: {.foo} Hi ::: :::::: .Hi :::
```````````````````````````````` Instead of a normal attribute specifier in curly braces, a single bare word may be used; it will be treated as a "class" attribute: ```````````````````````````````` example ::: c_d Hi ::: .Hi
Hi
This is some text!1. Other text.2.
Here's a thing3.
And another thing4.
This doesn't have a referent[^nope].
Hi!
Some bolded footnote definition.
Blockquotes can be in a footnote.
as well as code blocks
or, naturally, simple paragraphs.
no code block here (spaces are stripped away)
this is now a code block (8 spaces indentation)
This is unused.
Hello1
Footnote containing a list2
first
second
third
Hello
there
Hello
there
See the Heading above.
```````````````````````````````` ```````````````````````````````` example {#foo} # Heading See the [Heading] above. .See the Heading above.
```````````````````````````````` Explicitly defined references take precedence: ```````````````````````````````` example # Heading See the [Heading] above. [Heading]: foo .See the Heading above.
```````````````````````````````` When there are two headings with the same text, the first takes precedence: ```````````````````````````````` example # Heading # Heading See the [Heading] above. .See the Heading above.
```````````````````````````````` Empty headings don't create implicit references: ```````````````````````````````` example # ## See [] and [ ]. .See [] and [ ].
```````````````````````````````` commonmark-extensions-0.2.3.6/test/math.md 0000644 0000000 0000000 00000004156 07346545000 016651 0 ustar 00 0000000 0000000 # TeX Math Inline math goes between `$` characters, and display math goes between `$$`: ```````````````````````````````` example Let $x$ and $y$ be integers such that $$x=y + 2$$ .Let \(x\) and \(y\) be integers such that \[x=y + 2\]
```````````````````````````````` In inline math, the opening `$` must not be followed by a whitespace, and the closing `$` must not be preceeded by whitespace. ```````````````````````````````` example This is not math: 2000$. And neither is this $ 4 $. Or this $4 $. .This is not math: 2000$. And neither is this $ 4 $. Or this $4 $.
```````````````````````````````` Display math delimiters can be surrounded by whitespace: ```````````````````````````````` example This is display math: $$ e=mc^2 $$ .This is display math: \[ e=mc^2 \]
```````````````````````````````` Note that math can contain embedded math. In scanning for a closing delimiter, we skip material in balanced curly braces: ```````````````````````````````` example This is display math: $$ \text{Hello $x^2$} $$ And this is inline math: $\text{Hello $x$ there!}$ .This is display math: \[ \text{Hello $x^2$} \] And this is inline math: \(\text{Hello $x$ there!}\)
```````````````````````````````` To avoid treating currency signs as math delimiters, one may occasionally have to backslash-escape them: ```````````````````````````````` example The cost is between \$10 and 30$. .The cost is between $10 and 30$.
```````````````````````````````` Dollar signs must also be backslash-escaped if they occur within math: ```````````````````````````````` example $\text{\$}$ .\(\text{\$}\)
```````````````````````````````` Everthing inside the math construction is treated as math, and not given its normal commonmark meaning. ```````````````````````````````` example $bc$ .\(b<a>c\)
```````````````````````````````` commonmark-extensions-0.2.3.6/test/pipe_tables.md 0000644 0000000 0000000 00000013052 07346545000 020202 0 ustar 00 0000000 0000000 ## Tables (extension) GFM enables the `table` extension, where an additional leaf block type is available. A [table](@) is an arrangement of data with rows and columns, consisting of a single header row, a [delimiter row] separating the header from the data, and zero or more data rows. Each row consists of cells containing arbitrary text, in which [inlines] are parsed, separated by pipes (`|`). A leading and trailing pipe is also recommended for clarity of reading, and if there's otherwise parsing ambiguity. Spaces between pipes and cell content are trimmed. Block-level elements cannot be inserted in a table. The [delimiter row](@) consists of cells whose only content are hyphens (`-`), and optionally, a leading or trailing colon (`:`), or both, to indicate left, right, or center alignment respectively. ```````````````````````````````` example | foo | bar | | --- | --- | | baz | bim | .| foo | bar |
|---|---|
| baz | bim |
| abc | defghi |
|---|---|
| bar | baz |
| f|oo |
|---|
b | az |
| b | im |
| abc | def |
|---|---|
| bar | baz |
```````````````````````````````` ```````````````````````````````` example | abc | def | | --- | --- | | bar | baz | bar .bar
| abc | def |
|---|---|
| bar | baz |
bar
```````````````````````````````` ```````````````````````````````` example | abc | def | | --- | --- | | bar | baz | bar .| abc | def |
|---|---|
| bar | baz |
bar
```````````````````````````````` The header row must match the [delimiter row] in the number of cells. If not, a table will not be recognized: ```````````````````````````````` example | abc | def | | --- | | bar | .| abc | def | | --- | | bar |
```````````````````````````````` The remainder of the table's rows may vary in the number of cells. If there are a number of cells fewer than the number of cells in the header row, empty cells are inserted. If there are greater, the excess is ignored: ```````````````````````````````` example | abc | def | | --- | --- | | bar | | bar | baz | boo | .| abc | def |
|---|---|
| bar | |
| bar | baz |
| abc | def |
|---|
| Not enough table | to be considered table |
| Not enough table | to be considered table | | Not enough table | to be considered table |
| ---- | --- |
```````````````````````````````` A table may be indented up to three spaces: ```````````````````````````````` example a | b | c - | - | - .| a | b | c |
|---|
a | b | c
- | - | -
| Too much table | to be considered table | | Too much table | to be considered table | |----------------|------------------------| | Too much table | to be considered table |
```````````````````````````````` Other block structures, like headers, have higher priority than tables. Tables can be nested in other elements, but don't benefit from laziness. ```````````````````````````````` example # abc | def ------|----- > abc | def > ----|----- > abc | def ----|----- .------|-----
abc def
```````````````````````````````` commonmark-extensions-0.2.3.6/test/raw_attribute.md 0000644 0000000 0000000 00000001751 07346545000 020572 0 ustar 00 0000000 0000000 A "raw attribute" is an `=` plus an alphanumeric string, in braces, like {=html5} If attached to an inline code span, it causes the span to be interpreted as raw inline content with the specified format. If attached to a fenced code block, it causes the block to be interpreted as raw block content with the specified format. A raw attribute may not occur together with other attributes. ```````````````````````````````` example ``` {=html} foo ``` . foo ```````````````````````````````` ```````````````````````````````` example `foo`{=html} .abc | def ----|-----
foo
```````````````````````````````` You can't mix regular and raw attributes: ```````````````````````````````` example ``` {=html #id} foo .<b>foo</b>
<b>foo</b>{=html .bar}
“Hello,” said the spider. “‘Shelob’ is my name.”
```````````````````````````````` ```````````````````````````````` example 'A', 'B', and 'C' are letters. .‘A’, ‘B’, and ‘C’ are letters.
```````````````````````````````` ```````````````````````````````` example 'Oak,' 'elm,' and 'beech' are names of trees. So is 'pine.' .‘Oak,’ ‘elm,’ and ‘beech’ are names of trees. So is ‘pine.’
```````````````````````````````` ```````````````````````````````` example 'He said, "I want to go."' .‘He said, “I want to go.”’
```````````````````````````````` A single quote that isn't an open quote matched with a close quote will be treated as an apostrophe: ```````````````````````````````` example Were you alive in the 70's? .Were you alive in the 70’s?
```````````````````````````````` ```````````````````````````````` example Here is some quoted '`code`' and a "[quoted link](url)". .Here is some quoted ‘code’ and a “quoted link”.
’tis the season to be ‘jolly’
```````````````````````````````` Multiple apostrophes should not be marked as open/closing quotes. ```````````````````````````````` example 'We'll use Jane's boat and John's truck,' Jenna said. .‘We’ll use Jane’s boat and John’s truck,’ Jenna said.
```````````````````````````````` An unmatched double quote will be interpreted as a left double quote, to facilitate this style: ```````````````````````````````` example "A paragraph with no closing quote. "Second paragraph by same speaker, in fiction." .“A paragraph with no closing quote.
“Second paragraph by same speaker, in fiction.”
```````````````````````````````` A quote following a `]` or `)` character cannot be an open quote: ```````````````````````````````` example [a]'s b' .[a]’s b’
```````````````````````````````` Quotes that are escaped come out as literal straight quotes: ```````````````````````````````` example \"This is not smart.\" This isn\'t either. 5\'8\" ."This is not smart." This isn't either. 5'8"
```````````````````````````````` Doubled quotes are treated as nested: ```````````````````````````````` example ''hi'' .‘‘hi’’
```````````````````````````````` Two hyphens form an en-dash, three an em-dash. ```````````````````````````````` example Some dashes: em---em en--en em --- em en -- en 2--3 .Some dashes: em—em en–en em — em en – en 2–3
```````````````````````````````` A sequence of more than three hyphens is parsed as a sequence of em and/or en dashes, with no hyphens. If possible, a homogeneous sequence of dashes is used (so, 10 hyphens = 5 en dashes, and 9 hyphens = 3 em dashes). When a heterogeneous sequence must be used, the em dashes come first, followed by the en dashes, and as few en dashes as possible are used (so, 7 hyphens = 2 em dashes an 1 en dash). ```````````````````````````````` example one- two-- three--- four---- five----- six------ seven------- eight-------- nine--------- thirteen-------------. .one- two– three— four–– five—– six—— seven—–– eight–––– nine——— thirteen———––.
```````````````````````````````` Hyphens can be escaped: ```````````````````````````````` example Escaped hyphens: \-- \-\-\-. .Escaped hyphens: -- ---.
```````````````````````````````` Three periods form an ellipsis: ```````````````````````````````` example Ellipses...and...and.... .Ellipses…and…and….
```````````````````````````````` Periods can be escaped if ellipsis-formation is not wanted: ```````````````````````````````` example No ellipses\.\.\. .No ellipses...
```````````````````````````````` commonmark-extensions-0.2.3.6/test/strikethrough.md 0000644 0000000 0000000 00000002045 07346545000 020615 0 ustar 00 0000000 0000000 ## Strikethrough Basic strikethrough is between two tildes: ```````````````````````````````` example ~~This is *stricken out*~~ .This is stricken out
~This is nothing~
```````````````````````````````` Backslash escapes: ```````````````````````````````` example ~~This is \~\~stricken~~ .This is ~~stricken
Thisisstricken
Thisisstricken
Here I strike out an exclamation point!.
E=mc2.
```````````````````````````````` Backslash escapes: ```````````````````````````````` example E=mc\~2\~. .E=mc~2~.
```````````````````````````````` Spaces and formatting are allowed: ```````````````````````````````` example E=mc~2 or *3*~. .E=mc2 or 3.
```````````````````````````````` Punctuation is ignored for purposes of determining flankingness: ```````````````````````````````` example E=mc~!~. .E=mc!.
```````````````````````````````` Subscript can't begin or end with a space: ```````````````````````````````` example E=mc~ 2~. E=mc~2 ~. ~ ~ .E=mc~ 2~.
E=mc~2 ~.
~ ~
```````````````````````````````` commonmark-extensions-0.2.3.6/test/superscript.md 0000644 0000000 0000000 00000001471 07346545000 020300 0 ustar 00 0000000 0000000 ## Superscript Basic superscript is between `^`s: ```````````````````````````````` example E=mc^2^. .E=mc2.
```````````````````````````````` Backslash escapes: ```````````````````````````````` example E=mc\^2\^. .E=mc^2^.
```````````````````````````````` Spaces and formatting are allowed: ```````````````````````````````` example E=mc^2 or *3*^. .E=mc2 or 3.
```````````````````````````````` Punctuation is ignored for purposes of determining flankingness: ```````````````````````````````` example E=mc^!^. .E=mc!.
```````````````````````````````` Superscript can't begin or end with a space: ```````````````````````````````` example E=mc^ 2^. E=mc^2 ^. ^ ^ .E=mc^ 2^.
E=mc^2 ^.
^ ^
```````````````````````````````` commonmark-extensions-0.2.3.6/test/task_lists.md 0000644 0000000 0000000 00000001321 07346545000 020067 0 ustar 00 0000000 0000000 ## Task lists As in GitHub-flavored Markdown. ```````````````````````````````` example - [ ] an unchecked task list item - [x] checked item .an unchecked task list item
with two paragraphs
checked item
![\"image\"](\"chap1/foo.jpg\")
"
, "![\"image\"](\"extra/baz.png\")
"
, "![\"image\"](\"/absolute/path.jpg\")
![link](\"http://example.com/foo.jpg\"){kind=link}