Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Invalid Atom feeds for code includes… #510
That sounded like a good idea at the time, but I have struggled a bit with some feed parsers choking on my feeds, and recently when investigating Atom for something else, I happened on this paragraph: “If type="html", then this element contains entity escaped html.”.
RFC 42 that defines the Atom syndication format also says “If the value of "type" is "html", the content of atom:content MUST NOT contain child elements […] The HTML markup MUST be escaped;”
I’m convinced that the use of CDATA instead of escaping the content is what causes some feed parsers to choke on our content. It might not be a direct violation of the spec, but I think it's close enough to cause confusion.
In my naïve hope that I’d found a simple solution to all my problems, I tried changing my feed content to this:
However, that brings me right back where I started, because some of Octopress’ enhancements are only applied after the template is rendered, which result in a broken feed intermixed with HTML, as seen here: http://mikkel.hoegh.org/blog/categories/drupal/atom.xml
Is there a way we can force Octopress to render its extensions in the template, so we can escape their output markup properly?