-
Notifications
You must be signed in to change notification settings - Fork 138
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
Angle bracket enclosed URL in reference link fails. #33
Comments
I agree, that's a bug. (Note: multimarkdown uses peg-markdown There are other implementations that fail also: I'm not actively maintaining peg-markdown any more, so I may not get |
@jgm thanks for the very informative reply. Is babelmark2 open source? In particular, I would like to see the normalization code, and how you are calling each engine to use it on the Markdown Test Suite. I meant in no way that you should fix this yourself: just filling the database =) I recommend putting either a "deprecated in favor of" or "looking for maintainers" notice on the repo description or at the top of the README. You got me curious now: the other thing you are working on is it closed source? Is it another markdown engine? What language will it be written on? |
babelmark2 isn't currently open source, but I'm using the To call the different engines, I just make HTTP requests. See the FAQ The new thing I'm working on is a complete spec and very comprehensive |
Cool. The markdown test suite also aims at making a spec: https://github.com/karlcow/markdown-testsuite/blob/master/markdown-spec.html, but is still too basic. The tests on the other hand are good I think: 103 total. Hope both projects can work together as closely as possible. |
Input:
The output
href
contains<>
, but the original docs http://daringfireball.net/projects/markdown/syntax#link say it should work:and it works on every major implementation except multi markdown.
If I could turn back time, I would not allow angle brackets like your implementation: it is better to have a single way of doing things.
But what is done is done, so until we have a markdown specification, it is better to be compatible IMHO.
Discovered with the Markdown Test Suite at karlcow/markdown-testsuite#50 . Congrats: this is the only failing test!
The text was updated successfully, but these errors were encountered: