Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-06-23 | Add tests to check that markdown parsing is working fine after an HTML block ↵ | Alexandre Mutel | |
end tag | |||
2016-06-20 | Cleaned up terminology around lazy continuation lines. | John MacFarlane | |
Added some links. | |||
2016-06-20 | Merge pull request #407 from samestep/master | John MacFarlane | |
Fix typos | |||
2016-06-19 | Fix capitalization error | Sam Estep | |
2016-06-18 | Remove broken link | Sam 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-04 | Merge pull request #406 from coding-horror/master | John MacFarlane | |
make interact more button-like and clearer | |||
2016-06-04 | make interact more button-like and clearer | Jeff Atwood | |
2016-06-02 | spec_tests.py: exit code is sum of failures and errors. | John MacFarlane | |
2016-06-02 | spec_tests.py: specify newline when opening file. | John MacFarlane | |
2016-05-31 | Fixed typo. Closes #402. | John MacFarlane | |
2016-05-24 | Added point about readibility to "What is Markdown" section. | John MacFarlane | |
2016-04-04 | Merge pull request #400 from robinst/example-for-blank-item-with-spaces | John MacFarlane | |
Add example for list item starting with a blank line with spaces | |||
2016-04-05 | Add example for list item starting with a blank line with spaces | Robin 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-24 | Updated spec version to 0.25. | John MacFarlane | |
2016-03-24 | Updated changelog. | John MacFarlane | |
2016-03-16 | Merge pull request #397 from OlsonDev/patch-1 | John MacFarlane | |
Add closing paranthesis to README.md | |||
2016-03-16 | Add closing paranthesis to README.md | Josh Olson | |
2016-02-06 | Added two more tab-handling cases. | John MacFarlane | |
2016-02-06 | Fixed initial spaces in blockquote/tab example. | John MacFarlane | |
2016-02-05 | Added another tab test. | John MacFarlane | |
Code block with partially consumed tab. | |||
2016-02-05 | Fixed 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-05 | Added another test for proper tab behavior. | John MacFarlane | |
See jgm/cmark#101 | |||
2016-01-26 | Merge pull request #390 from pra85/patch-1 | John MacFarlane | |
Update license year range to 2016 | |||
2016-01-26 | Update license year range to 2016 | Prayag Verma | |
2016-01-23 | Fixed typo: setext heading line -> setext heading underline. | John MacFarlane | |
Closes #389. | |||
2016-01-13 | Fixed date 2015->2016 (closes #388) | John MacFarlane | |
2016-01-12 | Version 0.24, changed date. | John MacFarlane | |
2016-01-12 | Updated changelog. | John MacFarlane | |
2016-01-11 | Added an example illustrating basic escaping of `(` inside link dest. | John MacFarlane | |
2016-01-10 | New 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-07 | Made compatibility notes for setext headings into spec tests. | John MacFarlane | |
2016-01-07 | Modified 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-05 | Disallow 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-05 | Added 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-05 | Removed 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-31 | CommonMark.dtd - allow item in custom_block. | John MacFarlane | |
2015-12-30 | Removed 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-30 | Changed misleading undefined entity name example. | John MacFarlane | |
2015-12-30 | Call FFFD the REPLACEMENT CHARACTER. | John MacFarlane | |
Not "unknown code point character." | |||
2015-12-28 | Updated changelog.txt. | John MacFarlane | |
2015-12-28 | Change version to 0.23. | John MacFarlane | |
2015-12-28 | Don't allow space between link text and link label | John MacFarlane | |
in a reference link. This fixes the problem of inadvertent capture: [foo] [bar] [foo]: /u1 [bar]: /u2 | |||
2015-12-28 | Added 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-28 | Normalize URLs in test suite. | John MacFarlane | |
This way we don't fail tests for legitimate variations in URL escaping/normalization policies. Closes #334. | |||
2015-12-28 | Clarified that spec does not dictate URL encoding/normalization policy. | John MacFarlane | |
2015-12-28 | Shortened example that wrapped. | John MacFarlane | |
Closes #371. | |||
2015-12-28 | ATX headers: clarify that a space (or EOL) is needed. | John MacFarlane | |
Other whitespace won't do. Added a test case and modified an existing one to make this clearer. Closes #373. | |||
2015-12-28 | Minor improvements to entity section. | John MacFarlane | |
2015-12-28 | Fixed small regression in makespec.py. | John MacFarlane | |
2015-12-28 | makespec.py: remove need for link anchors to be on one line. | John MacFarlane | |