em formatting issues using underscore (_)

[oliversturm]

Delimiting underscores are not detected correctly if they are followed by commas. Here's a snippet that demonstrates the issue:

_This should be em_, but the end is not detected correctly due to the comma.

_If I have some em_, followed by a comma, and then _some further em_ that's detected correctly, the two are combined.

The result of passing this text through marked 0.5.2 is this:

<p>_This should be em_, but the end is not detected correctly due to the comma.</p>
<p><em>If I have some em_, followed by a comma, and then _some further em</em> that’s detected correctly, the two are combined.</p>

As you can see, several underscores are still included in the HTML output, and the two "em" parts in the second paragraph have been combined incorrectly.

The CommonMark Demo formats the output as expected, leaving no underscores in the HTML.

[UziTech]

Thanks for reporting this.

CommonMark demo

<p><em>This should be em</em>, but the end is not detected correctly due to the comma.</p>
<p>_If I have some em _, followed by a comma, and then <em>some further em</em> that's detected correctly, the two are combined.</p>

marked demo

<p>_This should be em_, but the end is not detected correctly due to the comma.</p>
<p><em>If I have some em_, followed by a comma, and then _some further em</em> that&#39;s detected correctly, the two are combined.</p>

[styfle]

I believe this is fixed on master. Maybe we should release soon?

[oliversturm]

@UziTech I see you copied some results into your comment. Just to keep things very clear here - I think you made a mistake - the CommonMark output I see is this (note the second line is different from yours):

<p><em>This should be em</em>, but the end is not detected correctly due to the comma.</p>
<p><em>If I have some em</em>, followed by a comma, and then <em>some further em</em> that's detected correctly, the two are combined.</p>

[UziTech]

looks like this was fixed in 0.6.0

[oliversturm]

Confirmed: my original test cases render correctly now. Thanks for the update!