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
Standard behavior without any flags seems to be to expand literal ampersands in the markdown input to produce & in the html output and to interpret other character entities in the input to produce unicode characters in the output. For example: # in the input produces # in the output.
When --fverbatim-entities is given, I would expect that entities are not interpreted in any way, and instead passed through the markdown interpreter to produce the same entity in the html output.
I am using the current version installed from Manjaro's repositories.
Standard behavior without any flags seems to be to expand literal ampersands in the markdown input to produce
&
in the html output and to interpret other character entities in the input to produce unicode characters in the output. For example:#
in the input produces # in the output.This is fine, but when --fverbatim-entities is used, the literal ampersand in the character entity in the mardown input is still expanded to
&
When --fverbatim-entities is given, I would expect that entities are not interpreted in any way, and instead passed through the markdown interpreter to produce the same entity in the html output.
I am using the current version installed from Manjaro's repositories.
The text was updated successfully, but these errors were encountered: