Age | Commit message (Collapse) | Author | |
---|---|---|---|
2014-11-09 | Added clarification that hard breaks don't work at ends of blocks. | John MacFarlane | |
Closes #191. | |||
2014-11-09 | Spec: use terminology of "image description" rather than "alt text". | John MacFarlane | |
"alt text" has to do with one possible rendering decision. | |||
2014-11-09 | Fixed spec tests. | John MacFarlane | |
2014-11-09 | Fixed 2 typos in spec tests. | John MacFarlane | |
2014-11-09 | Updated spec for links. | John MacFarlane | |
Still a work in progress. | |||
2014-11-08 | Spec: 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-06 | Bump version on spec to 0.10. | John MacFarlane | |
2014-11-06 | Spec: 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 <em>bar</em>`. | |||
2014-11-04 | Bump version on spec to 0.9. | John MacFarlane | |
2014-11-04 | Rewrote emph/strong part of spec, with more systematic examples. | John MacFarlane | |
2014-11-03 | Update spec version. | John MacFarlane | |
2014-11-03 | Removed 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-28 | Update spec version. | John MacFarlane | |
2014-10-28 | Clarified 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-27 | Updated spec date/version. | John MacFarlane | |
2014-10-26 | Require space before closing # sequence in ATX header. | John MacFarlane | |
Closes #169. | |||
2014-10-26 | Tweaked the closing fence section added in last commit. | John MacFarlane | |
2014-10-26 | Merge pull request #116 from Bengt/code_block_closing_fences | John MacFarlane | |
Add example from issue #94 about indented code block closing fences | |||
2014-10-25 | Wording change on tight/loose list example. | John MacFarlane | |
See #91. | |||
2014-10-25 | Added anchors for `tight` and `loose`. | John MacFarlane | |
See #91. | |||
2014-10-25 | Added hard-line-break anchor and links. | John MacFarlane | |
See #91. | |||
2014-10-25 | Fixed typo: code block -> HTML block. | John MacFarlane | |
See #91. | |||
2014-10-25 | Clarified mention of "lazy line" with link and further example. | John MacFarlane | |
See #91. | |||
2014-10-25 | Updated spec date/version. | John MacFarlane | |
2014-10-25 | Spec: Resolve hrule/setext header ambiguity. | John MacFarlane | |
Closes #31. | |||
2014-10-25 | Spec: Clarify that a list can interrupt a paragraph. | John MacFarlane | |
Include a discussion of the principle of uniformity that motivates this. Closes #26. | |||
2014-10-24 | Spec version to 0.4. | John MacFarlane | |
2014-10-24 | Spec: improved an example for hrules. | John MacFarlane | |
Suggestion due to BrendanLong from http://talk.commonmark.org/t/example-16-is-potentially-confusing/114 | |||
2014-10-24 | Spec: say explicitly that a character is a unicode code point. | John MacFarlane | |
2014-10-24 | Spec: Added rule clarifying setext header content. | John MacFarlane | |
Also several test cases. Closes #13. | |||
2014-10-24 | Spec: altered processing instruction test. | John MacFarlane | |
This catches the edge case described in #117. | |||
2014-10-24 | Added test case with heading in list item. | John MacFarlane | |
2014-10-24 | Fixed typo. Closes #110. | John MacFarlane | |
2014-10-24 | Update version and date on spec. | John MacFarlane | |
Switch to an 0.x version number to indicate more clearly that this is provisional. | |||
2014-10-24 | More tweaks on emph/strong spec and tests. | John MacFarlane | |
2014-10-24 | Removed test case with only opening emph markers. | John MacFarlane | |
It's not big enough to reveal stack problems. | |||
2014-10-24 | Added tricky recursive case for emph/strong. | John MacFarlane | |
2014-10-24 | Revised spec for new emph/strong rules. | John MacFarlane | |
These rules go with the new stack-based parser for emph/strong. | |||
2014-10-08 | Remove duplicate `footer` | Will Bond | |
2014-10-07 | Added cases from #51 to spec. | John MacFarlane | |
Closes #51. | |||
2014-10-07 | Added test case from issue #147. | John MacFarlane | |
2014-10-07 | Merge branch 'master' into newemphasis | John MacFarlane | |
Conflicts: spec.txt | |||
2014-10-07 | Cleaned up entity section of spec. | John MacFarlane | |
We convert entities to unicode characters, not UTF-8 sequences. (Though they might ultimately be output that way.) | |||
2014-10-07 | Adjusted tests for new js parser. | John MacFarlane | |
2014-10-07 | Removed spurious 'and', reflowed. | John MacFarlane | |
2014-10-07 | Removed spurious 'and', reflowed. | John MacFarlane | |
2014-10-06 | Merge pull request #143 from aJanuary/patch-1 | John MacFarlane | |
Changes append to prepend | |||
2014-09-29 | Merge branch 'master' into newemphasis | John MacFarlane | |
Conflicts: Makefile js/stmd.js | |||
2014-09-29 | Adds missing newlines | Andrew January | |
2014-09-29 | Changes urls to use example.com | Andrew January | |
As per RFC 2606 it is recommended to use example.com for sample urls in specifications. One example is left using "foo+special@Bar.baz-bar0.com" because it is designed to demonstrate the complexity of email addresses that should be permitted. |