Re^3: Problems with HTML Encoding in RSS after moving to XML::RSS 1.48

I wonder about which renderer you are really talking about. I think Firefox itself doesn't render RSS. Whatever renderer it is, it appears to be buggy. < and < are equivalent in XML like 'abc' and "abc" are equivalent in Perl.

A browser can't tell the difference between a static file and a generated file, so there is another difference. That difference is probably the real problem.

Comment on Re^3: Problems with HTML Encoding in RSS after moving to XML::RSS 1.48 Select or Download Code

Replies are listed 'Best First'.
Re^4: Problems with HTML Encoding in RSS after moving to XML::RSS 1.48 by Corion (Patriarch) on Oct 22, 2010 at 19:06 UTC
Maybe the "problem" is that the closing angle brackets are not respectively are HTML-encoded (`>` vs `>`)? My short forays into generating HTML content for RSS make me think that all HTML needs to be entity-encoded so the XML remains valid, at least I (actually, XML::RSS::SimpleGen) do so with my Image photo stream RSS. You can add this as as "Smart bookmarks" in Firefox, which I think is how one could use Firefox as RSS reader. But without deeper knowledge and experience of RSS, I don't know. Personally, I consider the full-encoded RSS to be "more valid".	[reply] [d/l] [select]
Re^5: Problems with HTML Encoding in RSS after moving to XML::RSS 1.48 by ikegami (Patriarch) on Oct 22, 2010 at 22:25 UTC
XML doesn't require a "`>`" in text data to be encoded, but any character in text data can be encoded. Or maybe you're playing with the idea that it's not text data. If so, neither would work as both encode the "`<`" as if it was text data. Personally, I consider the full-encoded RSS to be "more valid". So you always escape "`!`", "`?`", "`[`", "`]`" and "`-`"? They are no more and no less special than "`>`". Each is a special character in the right context in XML, and each is perfectly ordinary in text data and attribute values.	[reply] [d/l] [select]