-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrectly decoding encoded HTML tags #106
Comments
apjones6
pushed a commit
to apjones6/to-markdown
that referenced
this issue
Sep 15, 2015
This is an actual issue for using turndown as a Markdown converter whenever using escaped HTML elements in the input format, as they will be incorrectly output as HTML tags. A quick hack to fix this is ensuring < and > are always re-encoded as entities. |
Duplicate issue: #261. |
bjones1
added a commit
to bjones1/turndown
that referenced
this issue
Jun 2, 2023
raw HTML and HTML blocks. Closes mixmark-io#106 Closes mixmark-io#261
bjones1
added a commit
to bjones1/turndown
that referenced
this issue
Aug 23, 2024
raw HTML and HTML blocks. Closes mixmark-io#106 Closes mixmark-io#261
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With a standard MD parser encoded HTML tags allows you to include them as readable text. For example (plain HTML included for comparison):
results in the output HTML:
However if I put this output HTML through to-markdown the encoded < and > characters are erroneously decoded. This results in the following markdown:
(whitespace lines removed from examples for brevity)
The text was updated successfully, but these errors were encountered: