mirror of
https://github.com/xoofx/markdig.git
synced 2026-02-04 05:44:50 +00:00
Wrong output while parsing markdown to html #243
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ShadowmourneE on GitHub (Nov 22, 2018).
Hi all,
For example I would like to parse such markdown expression:
"**_boldItailcs_**clean_italics_" ( the first word is bold and italics).Consequently, the output in HTML is following:
<p>**<em>boldItailcs</em>**clean_italics_</p>but should be for example
<p><strong><em>BOLD</em></strong>clean<em>XUYUS</em></p>@xoofx commented on GitHub (Nov 22, 2018):
Unfortunately what you are looking for is not a correct CommonMark markdown. You can see that all CommonMark implementations are rendering this in the same way
@Creta5164 commented on GitHub (Jan 26, 2020):
Uh, sorry for reopen this issue, I have found something weird behaviour.
In this case works well. (line 6)
It uses advenced extensions.
Test snippet(markdig(advenced))
Perhaps these parts may not be intuitive in parsing criteria, I think.
Version : 0.18.0
@MihaZupan commented on GitHub (Jan 26, 2020):
Can you point out which part seems incorrect and what the expected output would be?
@Creta5164 commented on GitHub (Jan 26, 2020):
Originally, it's render like this.
But, when remove first space in line 3, it'll be render without
strong.But inside of
em, that's rendered as expect well.This is might be confusing about this behaviour.
@Creta5164 commented on GitHub (Jan 26, 2020):
I have found when it ends with bracket then had problem, I think it's not like in this case.
Should I open new issue about this?
@Creta5164 commented on GitHub (Jan 26, 2020):
Uh, sorry for keep knocking this, common-mark have test case about this.
I'll finish this conversation, thank you for attention!
https://spec.commonmark.org/dingus/?text=*(*foo)%0A
@Creta5164 commented on GitHub (Jan 26, 2020):
Okay, if someone have looking about like this problem, this is how to do it.
Use HTML tag, instead markdown note.