Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move to the successor of sundown for markdown parsing, upon release #9377

Closed
thestinger opened this issue Sep 21, 2013 · 3 comments
Closed
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@thestinger
Copy link
Contributor

Pandoc is a very large dependency since it requires building a huge tree of Haskell libraries with GHC. It would be nice to use a slimmer dependency, but Markdown is very fragmented and almost every library invents a new poorly defined variant. We are going to want some features like tables that are entirely implementation-specific. Other users of Markdown of very aware of these problems, and seem to be settling on a defacto standard implementation:

https://github.com/vmg/sundown/blob/master/CONTRIBUTING.md

@thestinger
Copy link
Contributor Author

It doesn't look like this standardization effort went anywhere, so there's not really a point in keeping open an issue.

@lucab
Copy link
Contributor

lucab commented Oct 28, 2013

It looks like the replacement is mostly ready to go, see hoedown. They are also making tagged releases now.

Maybe this ticket can be reopened and done as part of #10103

@alexcrichton
Copy link
Member

We talked about this in a meeting recently, and for now we're going to stick with sundown. Hoedown does certainly look promising, but we didn't want to jump on the bandwagon too soon. We wanted to wait for a more general movement of the markdown community to using hoedown instead of using sundown (which may have happened, I'm not following it very closely).

For the time being though, we've explicitly opted to say with sundown instead of using hoedown (although that's not set in stone).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

3 participants