| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit ee779cb7f8ea3c6274aef89f9916931b907e211e.
|
|
This reverts commit 5ca9ca1d5e70cbfe8eeae12f96e761c405ad8f86.
|
|
Allow HTML blocks to end on the last line of their container
|
|
This reverts commit 85bd3b9b149bef97755f16538e9c01cc386f6e5b.
|
|
This reverts commit ee75eb33f9bdf6901388e5f9175834acca814e5c.
|
|
See #410.
|
|
See discussion here: https://github.com/jgm/commonmark.js/issues/103#issuecomment-228888648
|
|
Closes #410.
|
|
|
|
See
https://talk.commonmark.org/t/emphasis-strong-emphasis-corner-cases/2123
for motivation.
This restores intuitive parsings for a number of changes.
The main change is to disallow strong or emph when one of
the delimiters is "internal" and the sum of the lengths of
the enclosing delimiter runs is a multiple of 3.
Thus,
**foo*bar***
gets parsed `<strong>foo*bar</strong>` rather than
`<em><em>foo</em>bar</em>**` as before.
|
|
Improve tests for HTML end block parsing
|
|
end tag
|
|
|
|
Added some links.
|
|
|
|
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".
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
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
|
|
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.
|
|
|
|
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.
|
|
This matches the HTML5 meaning for the hr element, and
recognizes that the element may be rendered in various
ways (not always as a horizontal rule).
See http://talk.commonmark.org/t/horizontal-rule-or-thematic-break/912/3
IN the DTD hrule is renamed 'thematic_break'.
|
|
This avoids a confusion that might arise now that HTML5 has
a 'header' element, distinct from the 'headings' h1, h2, ...
Our headings correspond to HTML5 headings, not HTML5 headers.
The terminology of 'headings' is more natural, too.
The only thing going for 'header' is that John Gruber used
it in his original Markdown syntax description.
See
http://talk.commonmark.org/t/naming-of-h1-6-should-be-headings-not-headers-per-w3c/1871
|
|
This is to match cmark's output, since we test cmark
without normalization.
|
