Switched xml_escape for <![CDATA[]]> for post content #332
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See "Handling Atom Text and Content Constructs" (http://www.xml.com/pub/a/2005/12/07/handling-atom-text-and-content-constructs.html) for an explanation why this is valid and the recommended way of handling unescaped content in XML documents. TL;DR: Much nicer to read if you for some reason have a look at the feed.xml source. Also less parsing on the client-side.
|
I found just one failed test and fixed it. |
parkr
approved these changes
Jan 1, 2022
|
@jekyllbot: merge +fix |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See "Handling Atom Text and Content Constructs" (http://www.xml.com/pub/a/2005/12/07/handling-atom-text-and-content-constructs.html) for an explanation why this is valid and the recommended way of handling unescaped content in XML documents.
TL;DR: Much nicer to read if you for some reason have a look at the feed.xml source. Also less parsing on the client-side.