Skip to content
This repository has been archived by the owner on May 5, 2021. It is now read-only.

Test other markdown parsers and implement multiple renderers #39

Closed
angrykoala opened this issue Sep 7, 2016 · 2 comments
Closed

Test other markdown parsers and implement multiple renderers #39

angrykoala opened this issue Sep 7, 2016 · 2 comments
Labels
enhancement maintenance
Projects
yamp development
Milestone
0.4

Comments

@angrykoala
Copy link
Owner

Try marked as md2html parser and create a new renderer

Marked should be faster for rendering md2html, so it may be a good idea to implement a renderer based on marked, check if all functionality can be adapted (markdown-it plugins)
@angrykoala angrykoala added this to the 0.4 milestone Sep 7, 2016
@angrykoala angrykoala changed the title Implement and test a marked parser and renderer Implement and test other markdown parsers and renderers Sep 7, 2016
@angrykoala angrykoala changed the title Implement and test other markdown parsers and renderers Test other markdown parsers and implement multiple renderers Sep 7, 2016
@angrykoala
Copy link
Owner Author

Remarkable is another possible parser md2html

angrykoala pushed a commit that referenced this issue Sep 17, 2016
pdf renderer test #39
7b7e1b7
@angrykoala
Copy link
Owner Author

changed default md2html parser to marked as it has less dependencies, markdown-toc works correctly and it has bigger community

markdown-it plugins no longer supported

@angrykoala angrykoala mentioned this issue Oct 5, 2016
Closed
5 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement maintenance
Projects
No open projects
yamp development
Done
Milestone
0.4
Development

No branches or pull requests
1 participant
@angrykoala