summaryrefslogtreecommitdiff
path: root/spec.txt
AgeCommit message (Collapse)Author
2015-01-18Changed rule for `_` emphasis and strong emphasis.John MacFarlane
To prevent intra-word emphasis, we used to check to see if the delimiter was followed/preceded by an ASCII alphanumeric. We now do something more elegant: whereas an opening `*` must be left-flanking, an opening `_` must be left-flanking *and not right-flanking*. And so on for the other cases. All the original tests passed except some tests with Russian text with internal `_`, which formerly created emphasis but no longer do with the new rule. These tests have been adjusted. A few new test cases have been added to illustrate the rule. The C and JS implementations have both been updated.
2015-01-16Added spec example: loose list with blank line after fenced code.John MacFarlane
See #285. cmark currently fails this.
2015-01-14Bump spec version to 0.16.John MacFarlane
2015-01-14Rewrote beginning of Entities section.John MacFarlane
Clarified that only entities that are not in code blocks or code spans are decoded.
2015-01-14Inserted space (typo).John MacFarlane
See #284.
2015-01-14Removed defective Example 449.John MacFarlane
Closes #284.
2015-01-13Fixed typo in spec.John MacFarlane
Closes #283.
2015-01-11Added intended two-line hard-breaks in Examples 521, 523.John MacFarlane
Thanks to textnut for pointing out the mistake. <http://talk.commonmark.org/t/example-521-523-missing-2-spaces-at-line-end/1003/1>
2015-01-05Clarify that brackets in general don't take precedence over emph.John MacFarlane
Closes #258.
2015-01-05Clarify that final newline is removed from paragraph content.John MacFarlane
Closes #176.
2015-01-05Talk of "info string" rather than "attributes" for code blocks.John MacFarlane
Closes #262.
2015-01-05Clarified precedence of code spans, HTML tags, autolinks.John MacFarlane
Closes #259.
2015-01-05Fixed a number of links in spec.John MacFarlane
2015-01-04Fixed some duplicate references.John MacFarlane
2015-01-04Use cmark itself to build spec.html.John MacFarlane
Removes build dependency on pandoc. Closes #256. Note: we have lost "smart punctuation," but we can either (a) add an option to do this in the cmark renderer, or (b) insert unicode punctuation in the spec as needed. Not an urgent issue in any case.
2015-01-04Linkify "info string" in spec.John MacFarlane
2015-01-04Use shortcut reference links when possible in spec.txt.John MacFarlane
This relies on the new spec2md.py behavior of creating reference links for all internal anchors.
2015-01-03Moved non-comment examples (1e789d0f) to inline tag section.John MacFarlane
That's where they properly belong, since we deal with comments differently in blocks.
2015-01-03spec: Added examples of non-comments.John MacFarlane
See #264.
2015-01-03spec: use HTML5 spec's rule for HTML comments.John MacFarlane
2015-01-03Make clear that any sequence of characters is a valid document.John MacFarlane
Closes #266 in a slightly different way than @anko's PR.
2015-01-03Spec: "is preferred" -> "takes precedence".John MacFarlane
2015-01-02Minor reformatting.John MacFarlane
Ensure that labels for anchors don't break lines.
2015-01-02Regularized "non-space character" spelling and added links.John MacFarlane
Closes #260.
2015-01-02Use 4 spaces rather than 5 to show "four spaces is too much."John MacFarlane
Closes #261.
2014-12-31Spec to 0.15.John MacFarlane
2014-12-31Fixed some left-flanking/right-flanking reversals in spec for emphasis.John MacFarlane
Closes #257.
2014-12-31Bump spec version to 0.14.John MacFarlane
2014-12-31Added CC-BY-SA license to documentation.John MacFarlane
Closes #55.
2014-12-29spec: Define ascii punctuation character separately.John MacFarlane
That's because some ascii punctuation characters (like `<`) are not in a "P" character class (they are mathematical symbols). They need to be escapable so we'll treat them as "punctuation" here.
2014-12-27Spec: added example with two blank lines in fenced code in sublist.John MacFarlane
Actually I just tacked this on to the existing Example 170. Closes #180.
2014-12-27Clarify precedence of empty list item over setext header line.John MacFarlane
CLoses #95.
2014-12-27spec: Added rule for empty list item.John MacFarlane
Closes #242.
2014-12-27Spec: reworded principle of uniformity for more generality.John MacFarlane
It applies to all container blocks, not just list items.
2014-12-27spec: added another example of unclarity in Markdown syntax description.John MacFarlane
2014-12-25Fixed links to HTML5 spec.John MacFarlane
2014-12-25Fixed some broken anchors in the spec.John MacFarlane
2014-12-25Linkified "whitespace" in spec.John MacFarlane
Closes #108.
2014-12-25Added test case for link-in-link-in-image (#252).John MacFarlane
2014-12-25Improved rules for emphasis and strong emphasis.John MacFarlane
This improves parsing of emphasis around punctuation. Background: http://talk.commonmark.org/t/emphasis-inside-strong-broken-in-js-implementation-when-parenthesis-involved/903/6 The basic idea of the change is that if the delimiter is part of a delimiter clump that has punctuation to the left and a normal character (non-space, non-punctuation) to the right, it can only be an opener. If it has punctuation to the right and a normal character (non-space, non-punctuation) to the left, it can only be a closer. This handles cases like **Gomphocarpus (*Gomphocarpus physocarpus*, syn. *Asclepias physocarpa*)** and **foo "*bar*" foo** better than before. The spec section on Emphasis and Strong Emphasis has been extensively revised. The C and JS implementations have been brought up to date, and all tests pass.
2014-12-23Added definitions of whitespace and other character classes.John MacFarlane
Closes #108.
2014-12-14Clarify that unicode whitespace counts as whitespace in emph rules.John MacFarlane
Added a test case with a unicode nonbreaking space. See #108, though "whitespace" should still be defined more systematically. This is a step forward.
2014-12-13Clarified spec on indented code blocks.John MacFarlane
Previously the spec said, wrongly, that a blank line was needed between a paragraph and a following code block. It is only needed between a code block and a following paragraph (due to lazy continuations). Thanks to textnut for pointing this out.
2014-12-10Update spec version.John MacFarlane
2014-11-29Updated path for spec_test.py.John MacFarlane
2014-11-27Renamed runtests.py -> spec_tests.py.John MacFarlane
2014-11-25Rename NODE_STRING -> NODE_TEXT.John MacFarlane
In JS, use 'Text' instead of 'Str'. In spec, use "plain textual content" instead of "strings."
2014-11-24Add sentence about U+0000 to specNick Wellnhofer
Fixes #212.
2014-11-22Changed Example 196 in spec to reflect the spec's rules.John MacFarlane
This has no blank lines and so should not be a loose list. See #209.
2014-11-22Adjusted formatting of test - CR btw `<li>` and `<hr />`.John MacFarlane
This is consistent with treatment of other block elements in list items.