You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug has existed for a long time. It could be triggered as long as asterisks touch at least one side of parentheses, regardless of English or Chinese ones. Adding a space in-between could resolve it. .
In fact, there are many other cases where emphasis failed. But this one is quite typical and annoying among all.
Thanks for the report! I believe this is expected behavior, as pulldown-cmark closely follows CommonMark. In one of these cases, I believe it is the right-flanking delimiter rule which prevents it.
Unfortunately CommonMark does not handle scripts that don't have the same spacing characteristics as many western languages. I see several other people bring up this exact same issue on the forum, but unfortunately from the replies it doesn't look like it is likely to change in the foreseeable future. If pulldown-cmark were to support it, I think it would have to be as an extension.
In the meantime, you'll probably need to add or remove spaces to get it to work, or use HTML tags instead.
This bug has existed for a long time. It could be triggered as long as asterisks touch at least one side of parentheses, regardless of English or Chinese ones. Adding a space in-between could resolve it. .
In fact, there are many other cases where emphasis failed. But this one is quite typical and annoying among all.
Source:
Expected Result: (from pandoc)
Actual Result:
The text was updated successfully, but these errors were encountered: