summaryrefslogtreecommitdiff
path: root/spec.txt
AgeCommit message (Collapse)Author
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.
2014-11-22Added example to spec of shortcut link with following space.John MacFarlane
See #214.
2014-11-20Reformatted some spec examples to match output of cmark.John MacFarlane
This way cmark passes tests with `--no-normalize`. See #161.
2014-11-18Added python version of test runner.John MacFarlane
This tests the dynamic library when run without a second argument. The code makes use of an amended version of the normalization method from karlcow/markdown-testsuite. Closes #161.
2014-11-10Version 0.12.John MacFarlane
2014-11-10Added a link.John MacFarlane
2014-11-10Allow images to contain images.John MacFarlane
2014-11-10Bump spec version to 0.11.John MacFarlane
2014-11-09Added clarification that hard breaks don't work at ends of blocks.John MacFarlane
Closes #191.
2014-11-09Spec: use terminology of "image description" rather than "alt text".John MacFarlane
"alt text" has to do with one possible rendering decision.
2014-11-09Fixed spec tests.John MacFarlane
2014-11-09Fixed 2 typos in spec tests.John MacFarlane
2014-11-09Updated spec for links.John MacFarlane
Still a work in progress.
2014-11-08Spec: better system for designating definitions of terms.John MacFarlane
`[foo](@foo)` turns into an anchor with id `foo` that links to itself and has class `definition`. This allows us to remove the manual `<a>` tags in `spec.txt`. A simple regex substitution in the Makefile handles the transformation. I believe this addresses some of the concerns in #141 by giving the definitions a prominent appearance. Note that we want definitions to link to themselves, to allow users to quickly generate a link to the relevant bit of the spec.
2014-11-06Bump version on spec to 0.10.John MacFarlane
2014-11-06Spec: use plain string content of label for alt text in images.John MacFarlane
So, `foo bar` rather than `foo *bar*` or `foo <em>bar</em>` or `foo &lt;em&gt;bar&lt;/em&gt;`.
2014-11-04Bump version on spec to 0.9.John MacFarlane
2014-11-04Rewrote emph/strong part of spec, with more systematic examples.John MacFarlane
2014-11-03Update spec version.John MacFarlane
2014-11-03Removed artificial rule for emph/strong markers.John MacFarlane
Previously there was a rule that nothing in a string of more than 3 `*` or `_` characters could close or start emphasis. This was artifical and led to strange asymmetries, e.g. you could have `*a *b**` emph within emph but not `**a **b****` strong within strong. The new parsing strategy makes it easy to remove this limitation. Spec, js, and c implementations have been updated. Spec might need some further grooming.
2014-10-28Update spec version.John MacFarlane
2014-10-28Clarified emph/strong rules.John MacFarlane
Make it clear that in `**foo **bar baz**` the shorter of the two potential strong emphasis spans (`bar baz`) is preferred.
2014-10-27Updated spec date/version.John MacFarlane
2014-10-26Require space before closing # sequence in ATX header.John MacFarlane
Closes #169.
2014-10-26Tweaked the closing fence section added in last commit.John MacFarlane
2014-10-26Merge pull request #116 from Bengt/code_block_closing_fencesJohn MacFarlane
Add example from issue #94 about indented code block closing fences