aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2016-06-25Merge pull request #411 from mgeier/softbreak-linkJohn MacFarlane
Make "softbreak" a link target
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-23Merge pull request #408 from xoofx/nested_listJohn MacFarlane
Add test case for nested lists with an indent > 4
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-20Merge pull request #407 from samestep/masterJohn MacFarlane
Fix typos
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-06-04Merge pull request #406 from coding-horror/masterJohn MacFarlane
make interact more button-like and clearer
2016-06-04make interact more button-like and clearerJeff Atwood
2016-06-02spec_tests.py: exit code is sum of failures and errors.John MacFarlane
2016-06-02spec_tests.py: specify newline when opening file.John MacFarlane
2016-05-31Fixed typo. Closes #402.John MacFarlane
2016-05-24Added point about readibility to "What is Markdown" section.John MacFarlane
2016-04-04Merge pull request #400 from robinst/example-for-blank-item-with-spacesJohn MacFarlane
Add example for list item starting with a blank line with spaces
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-03-24Updated changelog.John MacFarlane
2016-03-16Merge pull request #397 from OlsonDev/patch-1John MacFarlane
Add closing paranthesis to README.md
2016-03-16Add closing paranthesis to README.mdJosh Olson
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-26Merge pull request #390 from pra85/patch-1John MacFarlane
Update license year range to 2016
2016-01-26Update license year range to 2016Prayag Verma
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-12Updated changelog.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
2016-01-05Added a URI test and split one into several.John MacFarlane
The additional test ensures that URI schemes must be more than one character.
2016-01-05Removed whitelist of valid schemes.John MacFarlane
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
2015-12-31CommonMark.dtd - allow item in custom_block.John MacFarlane
2015-12-30Removed misleading claim about entity references in raw HTML.John MacFarlane
Entity references are not treated as literal text in raw HTML; they are just passed through.
2015-12-30Changed misleading undefined entity name example.John MacFarlane
2015-12-30Call FFFD the REPLACEMENT CHARACTER.John MacFarlane
Not "unknown code point character."
2015-12-28Updated changelog.txt.John MacFarlane
2015-12-28Change version to 0.23.John MacFarlane
2015-12-28Don't allow space between link text and link labelJohn MacFarlane
in a reference link. This fixes the problem of inadvertent capture: [foo] [bar] [foo]: /u1 [bar]: /u2
2015-12-28Added example with escaped backslash at end of link label.John MacFarlane
Closes #325. Worth having this example, since there was a bug to this effect.
2015-12-28Normalize URLs in test suite.John MacFarlane
This way we don't fail tests for legitimate variations in URL escaping/normalization policies. Closes #334.
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-16 08:48:04 +0000