I’m with Phil — I still don’t understand what the big deal about <xhtml:body> is for RSS feeds. What’s supposed to make it so much better than <content:encoded>?
BTW, Phil, as far as HTML entities go, if you just prefer to use things like “ rather than “, check out my RSS 2.0 feed.
Related posts:
- RSS Improvements
" I’ve added full-content <content:encoded> article text to my RSS 2.0 feed. Does anyone have any comments on whether I should use <xhtml:body> instead? I..."
- XHTML 2.0
" The W3C has released a new working draft for XHTML 2.0. As has been noted before, XHTML2 is very different from XHTML1, and XHTML1..."
- blo.gs update
" An update on the ongoing problem with blo.gs updates… Blo.gs is still reporting erroneous updates. Not as many as before, but still enough to..."
- Real World CSS
" For anyone who is still mired in the HTML Tag Soup of old-style web page design, the question, “Why should I switch to using..."
- WP-Cache fix for Content-Type in feeds
" If you run a busy WordPress site, or even if your site just has a lot of processor-intensive plugins, then you probably already run..."
xhtml:body
I’m with Phil — I still don’t understand what the big deal about <xhtml:body> is for RSS feeds. What’s supposed to make it so much better than <content:encoded>?
BTW, Phil, as far as HTML entities go, if you just prefer to use things like “ rather than “, check out my RSS 2.0 feed.
Related posts:
" I’ve added full-content <content:encoded> article text to my RSS 2.0 feed. Does anyone have any comments on whether I should use <xhtml:body> instead? I..."
" The W3C has released a new working draft for XHTML 2.0. As has been noted before, XHTML2 is very different from XHTML1, and XHTML1..."
" An update on the ongoing problem with blo.gs updates… Blo.gs is still reporting erroneous updates. Not as many as before, but still enough to..."
" For anyone who is still mired in the HTML Tag Soup of old-style web page design, the question, “Why should I switch to using..."
" If you run a busy WordPress site, or even if your site just has a lot of processor-intensive plugins, then you probably already run..."