| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2014-12-25 | JS: fixed parsing of link-in-link-in-image. | John MacFarlane | |
| Partially addresses #252. Still need to: - update C parser. - put an example in the spec. | |||
| 2014-12-25 | Fixed infinite loop in JS parser for link-in-link-in-image. | John MacFarlane | |
| Partially addresses #252. This fixes the infinite loop, and brings the JS parser into agreement with cmark, but both still have bad output in this case, so more work is needed. | |||
| 2014-12-25 | Improved 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-10 | Further delinting efforts. | John MacFarlane | |
| 2014-12-10 | More js delinting. | John MacFarlane | |
| 2014-12-10 | More js delinting. | John MacFarlane | |
| 2014-12-10 | More linter corrections to js code. | John MacFarlane | |
| 2014-12-10 | More eslint corrections. | John MacFarlane | |
| 2014-12-10 | linter fixes to html5-entities.js and index.js. | John MacFarlane | |
| 2014-12-10 | Fixed linter errors in js/bin/commonmark, js/test.js. | John MacFarlane | |
| 2014-12-10 | html5-entities.js: put object property 'in' in quotes. | John MacFarlane | |
| ...this is a JS keyword, and at least IE8 gets confused by it in this context. | |||
| 2014-12-09 | Avoid using non-ascii characters in js code. | John MacFarlane | |
| It seems to confuse IE8. | |||
| 2014-11-25 | Rename NODE_STRING -> NODE_TEXT. | John MacFarlane | |
| In JS, use 'Text' instead of 'Str'. In spec, use "plain textual content" instead of "strings." | |||
| 2014-11-23 | js: use 'CodeBlock' in AST for all code blocks. | John MacFarlane | |
| Don't distinguish fenced, indented. | |||
| 2014-11-23 | Revert "Revert "Remove distinction btw atx and setext header in AST."" | John MacFarlane | |
| This reverts commit 4570eb2bff2e1b71fa5b6408abbc69c98ff5ff24. | |||
| 2014-11-22 | Revert "Remove distinction btw atx and setext header in AST." | John MacFarlane | |
| This reverts commit a71423f6ee1b77d9f79d42599ea00b4ca99f5da0. Not quite sure about this change, so reverting for now. Note that we still have a distinction between fenced and indented code blocks in the AST. These two distinctions seem to stand or fall together. | |||
| 2014-11-22 | Remove distinction btw atx and setext header in AST. | John MacFarlane | |
| Now we just have 'header' -- Setext and ATX are just two ways of forming these; it's not a semantic difference that should remain in the AST. | |||
| 2014-11-22 | Fixed #192. | John MacFarlane | |
| The C and JS implementations were not registering blank lines after atx headers for purposes of tight/loose list calculation. Exmaple: * item * # block1 ## block2 | |||
| 2014-11-22 | Updated JS and C implementations for #209. | John MacFarlane | |
| A setext header was being treated a if it were a blank line for purposes of tight/loose list determination. Closes #209. | |||
| 2014-11-22 | js html renderer: formatting changes to align with changes in spec. | John MacFarlane | |
| 2014-11-22 | Fixed #214 C and JS implementations. | John MacFarlane | |
| They were gobbling whitespace after shortcut reference links, e.g. [foo] bar [foo]: url Closes #214. | |||
| 2014-11-17 | Fix Issue 202 - Catch RangeError thrown by native String.fromCodePoint (js ↵ | Guillaume Crico | |
| implementation) When using a JS engine that provides a native String.fromCodePoint ES6 implementation (e.g. SpiderMonkey), a RangeError is thrown if the codepoint is invalid. When adding the from-code-point.js polyfill, the js implementation was modified in order to handle invalid code point by returning the 0xFFFD placeholder glyph. So this is not a real "polyfill", but an specific implementation (adapted to the parser needs). So, if a native String.fromCodePoint implementation is availbale, the fromCodePoint function should catch the RangeError and return the 0xFFFD placeholder glyph. | |||
| 2014-11-11 | Bump version on package.json. | John MacFarlane | |
| 2014-11-10 | Allow images to contain images. | John MacFarlane | |
| 2014-11-10 | jshint improvements. | John MacFarlane | |
| 2014-11-10 | Stack-based link handling in js. All tests pass. | John MacFarlane | |
| 2014-11-09 | Rewrote parseLink in js consistent with the C and spec. | John MacFarlane | |
| 2014-11-09 | Added processEmphasis, run at end of parseInlines. | John MacFarlane | |
| 2014-11-09 | Changed parseEmphasis to just put things on stack. | John MacFarlane | |
| 2014-11-06 | Updated js writer to render plain text for alt attributes of images. | John MacFarlane | |
| 2014-11-04 | Added packaging for npm module 'commonmark'. | John MacFarlane | |
| Published to npm. Closes #21. The 'stmd' package should be deprecated. | |||
| 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-30 | js/lib/blocks: Made matchAt return -1 instead of null on no match. | John MacFarlane | |
| 2014-10-26 | Dingus improvements; moved to top level. | John MacFarlane | |
| 2014-10-26 | Added clear and permalink to dingus. | John MacFarlane | |
| Serve dingus from dingus.html. Add redirect page as index.html. | |||
| 2014-10-26 | Require space before closing # sequence in ATX header. | John MacFarlane | |
| Closes #169. | |||
| 2014-10-25 | Adjusted appearance of dingus. | John MacFarlane | |
| 2014-10-24 | Rename js/bin/markdown -> js/bin/commonmark. | John MacFarlane | |
| 2014-10-24 | js/bin/markdown: added `--ast` flag and multiple filename args. | John MacFarlane | |
| 2014-10-24 | Merge pull request #140 from arthur-peka/master | John MacFarlane | |
| Changing some variable names to improve code readability | |||
| 2014-10-24 | More stmd -> commonmark changes. | John MacFarlane | |
| 2014-10-24 | Renamed javascript implementation to commonmark.js. | John MacFarlane | |
| 2014-10-24 | js: Removed memoization. | John MacFarlane | |
| It is no longer needed with the new stack-based emphasis parsing. | |||
| 2014-10-24 | js: Use linked list instead of array for emphasis_openers stack. | John MacFarlane | |
| 2014-10-24 | js: renamed emph_stack -> emphasis_openers. | John MacFarlane | |
| 2014-10-23 | inlines.js: Implemented stack-based emph parsing. | John MacFarlane | |
| 2014-10-18 | Added renderAST to js, added AST render tab to dingus. | John MacFarlane | |
| Modified processInlines so it creates new objects instead of modifying in place. This way we can remove the extraneous fields only needed for parsing. | |||
| 2014-10-18 | Add unescapeString as method of InlineParser. | John MacFarlane | |
| 2014-10-18 | Factored out blocks.js from index.js. | John MacFarlane | |
| 2014-10-18 | Factored out inlines.js from index.js. | John MacFarlane | |
 |
index : cmark | |
| My own fork of cmark for commonmark conversion | KatolaZ |
| summaryrefslogtreecommitdiff |