aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
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.
2015-12-28Clarified that spec does not dictate URL encoding/normalization policy.John MacFarlane
2015-12-28Shortened example that wrapped.John MacFarlane
Closes #371.
2015-12-28ATX 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-28Minor improvements to entity section.John MacFarlane
2015-12-28Fixed small regression in makespec.py.John MacFarlane
2015-12-28makespec.py: remove need for link anchors to be on one line.John MacFarlane
2015-12-28Rewrote "Entities" section with more correct terminology.John MacFarlane
Entity references and numeric character references. Closes #375.
2015-12-28Fixed some HTML inline tests...John MacFarlane
which were actually HTML blocks, given the changes to block parsing rules since these examples were written. Closes #382.
2015-12-28DTD - Rename html -> html_block, inline_html -> html_inline.John MacFarlane
For consistency.
2015-12-28DTD - allow custom_block to contain either blocks or inlines children.John MacFarlane
2015-12-27dtd - added xmlns attribute to document, fixed typos.John MacFarlane
2015-12-27CommonMark.dtd - added custom_block, custom_inline.John MacFarlane
2015-12-23makespec.py: Only do two levels in the TOC.John MacFarlane
2015-12-22Rename 'horizontal rule' -> 'thematic break'.John MacFarlane
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'.
2015-12-22Rename 'header' -> 'heading'.John MacFarlane
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
2015-12-22Minor spacing adjustments in test output.John MacFarlane
This is to match cmark's output, since we test cmark without normalization.
2015-12-22Small adjustment to new test case for indented code in list.John MacFarlane
Reworded the description, added a case with two blank lines.
2015-12-22Merge pull request #384 from cmbrandenburg/empty_line_code_blockJohn MacFarlane
New test case: list item code block with empty line
2015-12-22New test case: list item code block with empty lineCraig M. Brandenburg
2015-12-21Merge pull request #383 from renzok/patch-1John MacFarlane
consistent usage of we instaed of I
2015-12-21consistent usage of we instaed of Irenzo
2015-11-23Better fix for #380.John MacFarlane
2015-11-23normalize.py: Don't use HTMLParseError.John MacFarlane
It has been removed as of python 3.5. Closes #380.
2015-10-19Modified specfilter.hs to account for last change.John MacFarlane
2015-10-19Use 'display:inline-block' rather than floats for side-by-side.John MacFarlane
This works when printed too.
2015-10-19Added better print CSS.John MacFarlane
2015-10-19Fixed duplicate id 'attribute'.John MacFarlane
2015-10-18Merge pull request #372 from lucaswerkmeister/fixLinkTargetsJohn MacFarlane
Fix four link targets
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-29 14:19:05 +0000