Age | Commit message (Collapse) | Author |
|
The term is actually labeled "paragraph continuation text", which
wouldn't fit in this sentence. Removing the link altogether is
consistent with other usages of "paragraph continuation line".
|
|
make interact more button-like and clearer
|
|
|
|
|
|
|
|
|
|
|
|
Add example for list item starting with a blank line with spaces
|
|
After implementing the changes for the 0.25 spec, all the spec tests
were green.
But I noticed that my code also counted the spaces on the first line and
required the subsequent lines to be indented accordingly. This example
catches that possible bug.
|
|
|
|
|
|
Add closing paranthesis to README.md
|
|
|
|
|
|
|
|
Code block with partially consumed tab.
|
|
In the blockquote with a tab following the `>`,
only one space should be consumed, yielding two
spaces at the beginning of the content.
|
|
See jgm/cmark#101
|
|
Update license year range to 2016
|
|
|
|
Closes #389.
|
|
|
|
|
|
|
|
|
|
The format for the spec examples has changed from
.
markdown
.
html
.
to
```````````````````````````````` example
markdown
.
html
````````````````````````````````
One advantage of this is that `spec.txt` becomes a valid
Markdown file.
`tests/spec_test.py` has been changed to use the new format.
The old `tools/makespec.py` has been replaced by a lua
program, `tools/make_spec.lua`, which uses the `lcmark` rock
(and indirectly libcmark). It can generate
html, latex, and commonmark versions of the spec.
Pandoc is no longer needed for the latex/PDF version.
And, since the new program uses the cmark API and operates
directly on the parse tree, we avoid certain bad results we
got with the regex replacements done by the python script.
|
|
|
|
Text like
Foo
bar
---
baz
is now interpreted as heading + paragraph, rather than
paragraph + thematic break + paragraph.
Existing implementations diverge quite a bit on this
case, with several interpretations:
1. paragraph, heading, paragraph
2. paragraph, break, paragraph
3. paragraph containing literal `---`
4. heading, paragraph
Interpretation 4 seems most natural, and it opens up an expressive
possibility otherwise closed off -- multiline headings.
Authors who want interpretation 2 can use a form that can't be
interpreted as a setext heading line, e.g.
Foo
bar
* * *
baz
or insert blank space around the thematic break.
Authors who want interpretation 3 can use backslash escapes.
Authors who want interpretation 1 can put a blank line
after the first paragraph.
|
|
See discussion at
http://talk.commonmark.org/t/minor-comments-and-unclarities-after-reading-the-spec/779
http://talk.commonmark.org/t/issues-to-resolve-before-1-0-release/1287/12
|
|
The additional test ensures that URI schemes must
be more than one character.
|
|
Now a scheme is any sequence of 2-32 characters, beginning
with an ASCII letter, and containing only ASCII letters,
digits, and the symbols `-`, `+`, `.`.
Changed several spec examples accordingly.
Discussion at
http://talk.commonmark.org/t/what-is-the-point-of-limiting-uri-schemes-in-autolinks/555/26
|
|
|
|
Entity references are not treated as literal text in
raw HTML; they are just passed through.
|
|
|
|
Not "unknown code point character."
|
|
|
|
|
|
in a reference link. This fixes the problem of
inadvertent capture:
[foo] [bar]
[foo]: /u1
[bar]: /u2
|
|
Closes #325.
Worth having this example, since there was a bug to this effect.
|
|
This way we don't fail tests for legitimate variations in
URL escaping/normalization policies.
Closes #334.
|
|
|
|
Closes #371.
|
|
Other whitespace won't do.
Added a test case and modified an existing one to
make this clearer.
Closes #373.
|
|
|
|
|
|
|
|
Entity references and numeric character references.
Closes #375.
|
|
which were actually HTML blocks, given the changes to
block parsing rules since these examples were written.
Closes #382.
|
|
For consistency.
|
|
|