aboutsummaryrefslogtreecommitdiff
path: root/spec.txt
AgeCommit message (Collapse)Author
2016-08-20Added closing paren. Fixes #428.John MacFarlane
2016-08-12Remove duplicated test.Maxim Dikun
Tests 390 and 391 are equal in 0.26.
2016-08-08Use fenced code blocks for markdown examples that are not test casesJohn MacFarlane
for uniformity.
2016-08-07Removed duplicate reference to "container block".John MacFarlane
2016-08-06Add examples for Unicode whitespaceTimothy Gu
In light of jgm/commonmark.js#107, add a few examples/test cases to make sure the distinction between Unicode whitespace and regular whitespace is kept.
2016-07-21Fix missing closing paren typoRobin Stocker
2016-07-20Update statement on blank lines and lists.Jesse Rosenthal
The definition of a list still said that "two blank lines end all containing lists." That rule has been removed.
2016-07-15Bump version to 0.26, update changelog.John MacFarlane
2016-07-13Merge pull request #417 from neongreen/patch-1John MacFarlane
Fix a typo in the spec
2016-07-13Moved restriction on paragraph-interrupting lists to list item specJohn MacFarlane
instead of list marker spec.
2016-07-13Empty list items cannot interrupt a paragraph.John MacFarlane
This removes an ambiguity between setext headers and lists in cases like foo -
2016-07-12Fix a typo in the specArtyom
2016-07-11Use <= instead of < for clarity.John MacFarlane
2016-07-11Removed the "two blank lines breaks out of lists" rule.John MacFarlane
This is incompatible with the principle of uniformity (and indeed with the spec for list items, which requires that the meaning of a chunk of lines not change when it is put into a list item.)
2016-07-11Ordered list markers that interrupt a paragraph must start with 1.John MacFarlane
2016-07-02Improved the section on tabs.John MacFarlane
Added some test cases for ATX headers and thematic breaks. Clarified that it's not just cases that affect indentation that matter, but all cases where whitespace matters for block structure.
2016-07-02Removed example of ATX header with tab after `#`.John MacFarlane
A tab ought to work; language at the beginning of the spec will be revised to make this clear.
2016-07-02Revert "Revert "Revert "ATX headers: clarify where tabs can go."""John MacFarlane
This reverts commit ee779cb7f8ea3c6274aef89f9916931b907e211e.
2016-07-02Revert "Clarified tab usage in thematic breaks."John MacFarlane
This reverts commit 5ca9ca1d5e70cbfe8eeae12f96e761c405ad8f86.
2016-07-01Merge pull request #412 from colinodell/patch-1John MacFarlane
Allow HTML blocks to end on the last line of their container
2016-06-27Revert "Revert "ATX headers: clarify where tabs can go.""John MacFarlane
This reverts commit 85bd3b9b149bef97755f16538e9c01cc386f6e5b.
2016-06-27Revert "ATX headers: clarify where tabs can go."John MacFarlane
This reverts commit ee75eb33f9bdf6901388e5f9175834acca814e5c.
2016-06-27ATX headers: clarify where tabs can go.John MacFarlane
See #410.
2016-06-27Allow HTML blocks to end on the last line of their containerColin O'Dell
See discussion here: https://github.com/jgm/commonmark.js/issues/103#issuecomment-228888648
2016-06-27Clarified tab usage in thematic breaks.John MacFarlane
Closes #410.
2016-06-25Make "softbreak" a link targetMatthias Geier
2016-06-24Spec changes in strong/emph parsing.John MacFarlane
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.
2016-06-23Merge pull request #409 from xoofx/html_end_parsingJohn MacFarlane
Improve tests for HTML end block parsing
2016-06-23Add tests to check that markdown parsing is working fine after an HTML block ↵Alexandre Mutel
end tag
2016-06-22Add test case for nested lists with an indent > 4Alexandre Mutel
2016-06-20Cleaned up terminology around lazy continuation lines.John MacFarlane
Added some links.
2016-06-19Fix capitalization errorSam Estep
2016-06-18Remove broken linkSam Estep
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".
2016-05-31Fixed typo. Closes #402.John MacFarlane
2016-05-24Added point about readibility to "What is Markdown" section.John MacFarlane
2016-04-05Add example for list item starting with a blank line with spacesRobin Stocker
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.
2016-03-24Updated spec version to 0.25.John MacFarlane
2016-02-06Added two more tab-handling cases.John MacFarlane
2016-02-06Fixed initial spaces in blockquote/tab example.John MacFarlane
2016-02-05Added another tab test.John MacFarlane
Code block with partially consumed tab.
2016-02-05Fixed spec test for tabs.John MacFarlane
In the blockquote with a tab following the `>`, only one space should be consumed, yielding two spaces at the beginning of the content.
2016-02-05Added another test for proper tab behavior.John MacFarlane
See jgm/cmark#101
2016-01-23Fixed typo: setext heading line -> setext heading underline.John MacFarlane
Closes #389.
2016-01-13Fixed date 2015->2016 (closes #388)John MacFarlane
2016-01-12Version 0.24, changed date.John MacFarlane
2016-01-11Added an example illustrating basic escaping of `(` inside link dest.John MacFarlane
2016-01-10New format for spec tests, new lua formatter for specs.John MacFarlane
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.
2016-01-07Made compatibility notes for setext headings into spec tests.John MacFarlane
2016-01-07Modified setext heading spec to allow multiline headings.John MacFarlane
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.
2016-01-05Disallow spaces in link destinations, even in pointy braces.John MacFarlane
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
generated by cgit v1.2.3 (git 2.46.0) at 2025-04-01 18:33:33 +0000