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
The markdown content should be parsed correctly, with the strong tag (**) properly converting text to bold, regardless of the presence of special characters or non-English text adjacent to the tags.
Actual behavior
When a colon character is present next to a strong tag with non-English text following it, the markdown syntax is not correctly parsed, and the raw markdown is displayed.
When non-English text is directly next to a strong tag without any special characters, the markdown is parsed correctly, and the text is bolded as expected.
Runtime
Node v17
Package manager
npm 8
OS
macOS
Build and bundle tools
Rollup
The text was updated successfully, but these errors were encountered:
Initial checklist
Affected packages and versions
"remark-gfm": "^4.0.0", "remark-parse": "^11.0.0", "unified": "^11.0.4"
Link to runnable example
No response
Steps to reproduce
remark-parse
,remark-gfm
, andunified
packages to parse markdown content.**
) is displayed instead of actual bold/strong text in the output, when there is a special character (here::
).markdownWithSpecialCharacter:
markdownWithoutSpecialCharacter:
Expected behavior
The markdown content should be parsed correctly, with the strong tag (**) properly converting text to bold, regardless of the presence of special characters or non-English text adjacent to the tags.
Actual behavior
Runtime
Node v17
Package manager
npm 8
OS
macOS
Build and bundle tools
Rollup
The text was updated successfully, but these errors were encountered: