-
Notifications
You must be signed in to change notification settings - Fork 14
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
Parser doesn't process markdown nested inside of HTML tags #28
Comments
You need to add
|
Thanks for the tip 🤗. We tried it to see what happens. |
Thanks so much for the explanation! I tried adding For example, given code:
Expected HTML:
Actual HTML:
|
@gettalong Please look into #28 (comment) |
@ashmaroli @charlottetan If you don't use the Is there any example where using a plain URL without enclosing angle brackets works? |
Using plain URLs works in Github's default readme, for example, see this file on this branch: |
@charlottetan I meant an example where this works with kramdown and parser-gfm. |
I'm confused, plain URLs work in Github's readme pages, are plain URLs not expected to work with kramdown+parser-gfm? |
parser-gfm doesn't use the parser from Github but a custom implementation. So it is not 100% compatible with GFM and this is a feature that is not yet implemented. |
Thank you @gettalong @charlottetan Until this feature gets implemented, (maybe, maybe not..), you may instruct kramdown to parse your standalone URLs and render them as links by surrounding each URL in angle brackets (
|
Looks like there's already a feature request for that with #17. |
For the following code snippet:
The expected HTML to be rendered is:
And GFM renders that perfectly:
https://github.com/EbookFoundation/free-programming-books/blob/e629db6b05a72fd64a6b33feeeebbe830641cf10/CONTRIBUTING-fa_IR.md
However kramdown-parser-gfm appears to stop processing any markdown once it is nested under an HTML tag
https://ebookfoundation.github.io/free-programming-books/CONTRIBUTING-fa_IR.html
See EbookFoundation/free-programming-books#5559 for more information
The text was updated successfully, but these errors were encountered: