uncorrect parsing result with very rare case #335

New Issue

claunia · 2026-01-29T14:34:04Z

claunia commented

2026-01-29 14:34:04 +00:00

Originally created by @kflili on GitHub (Oct 24, 2019).

Two cases:
Hello eudev@**microsoft.**com
Hello benefit of **$**225

Please the test link in below.
https://babelmark.github.io/?text=Hello+eudev%40microsoft.com%0A%0A+%0AHello+benefit+of+%24225

Originally created by @kflili on GitHub (Oct 24, 2019). Two cases: Hello eudev@**microsoft.**com Hello benefit of **$**225 ![image](https://user-images.githubusercontent.com/19175478/67444899-bb36cc00-f5bf-11e9-9ec6-88b5be2f484a.png) Please the test link in below. https://babelmark.github.io/?text=Hello+eudev%40**microsoft.**com%0A%0A+%0AHello+benefit+of+**%24**225

claunia closed this issue

2026-01-29 14:34:05 +00:00

claunia commented

2026-01-29 14:34:06 +00:00

@xoofx commented on GitHub (Oct 24, 2019):

It is correct for all CommonMark implementations and part of the specifications.

@xoofx commented on GitHub (Oct 24, 2019): It is correct for all CommonMark implementations and part of the specifications.

claunia commented

2026-01-29 14:34:06 +00:00

@kflili commented on GitHub (Oct 24, 2019):

CommonMark implementations and part of the specifications

@xoofx Thanks for the reply. Does that mean it meet the markdown standard, and should render as such? Our user want to get parsing upper results, not the lower results in the screenshot.

Any work around for this special case?

Thanks very much!

@kflili commented on GitHub (Oct 24, 2019): > CommonMark implementations and part of the specifications @xoofx Thanks for the reply. Does that mean it meet the markdown standard, and should render as such? Our user want to get parsing upper results, not the lower results in the screenshot. Any work around for this special case? Thanks very much!

claunia commented

2026-01-29 14:34:07 +00:00

@xoofx commented on GitHub (Oct 24, 2019):

Yes, it is the standard, so we can't change it. You can see also that on GitHub it is rendered like Markdig (because now GitHub is using a CommonMark compliant parser)

Hello eudev@**microsoft.**com
Hello benefit of **$**225

Any work around for this special case?

Apart developing a new emphasis parser by forking the default extension and replacing with your own, there is no easy workaround

@xoofx commented on GitHub (Oct 24, 2019): Yes, it is the standard, so we can't change it. You can see also that on GitHub it is rendered like Markdig (because now GitHub is using a CommonMark compliant parser) Hello eudev@**microsoft.**com Hello benefit of **$**225 > Any work around for this special case? Apart developing a new emphasis parser by forking the default extension and replacing with your own, there is no easy workaround

claunia commented

2026-01-29 14:34:08 +00:00

@kflili commented on GitHub (Oct 24, 2019):

Thanks @xoofx for the clear answer!

@kflili commented on GitHub (Oct 24, 2019): Thanks @xoofx for the clear answer!

claunia referenced this issue

2026-01-29 14:47:47 +00:00

[PR #336] [MERGED] Enhancements for YouTube Links #959

Sign in to join this conversation.