| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 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-10-18 | Change from-code-point.js so it doesn't alter String prototype. | John MacFarlane | |
| 2014-10-18 | Use browserify to make js code more modular. | John MacFarlane | |
| * Moved js library code to `js/lib`. * `js/stmd.js` is now generated from these files using browserify. * Factored out `html5-entities.js` and `from-code-point.js` from main js parsing code (which is now `index.js`). * Moved `js/markdown` to `js/bin`. | |||
 |
index : cmark | |
| My own fork of cmark for commonmark conversion | KatolaZ |
| summaryrefslogtreecommitdiff |