[bug] RSS 2.0 template

[deminy]

One of my friends told me that he was using Google Desktop Search to subscribe my RSS feed. The problem is: He could't see the contents of my blog from Google Desktop Search's toolbar(sidebar on your Windows's desktop), only titles were shown in the toolbar.

So later I checked the template file: templates/default/feed_2.0.tpl,
replaced the tag <content:encoded></content:encoded> with <description></description>. Now everything works fine for (all the) RSS readers reading my blog's RSS feed.

I was using s9y v1.0 beta 3 and now I am using s9y v1.0. Same problem happens.

[garvinhicking]

Hi!

This is not a bug of the RSS feed; "content:encoded" is properly valid according to RSS specs.

The problem is that s9y wants to show HTML content. However, the "<description>" field is by definition NOT allowed to hold HTML code.

So by using <description> we would either need to strip all HTML layout (which would suck) or we would be incompatible with the spec (which would suck). Thus we are using content:encoded, which allows it.

So it'S actually a bug the Google Desktop Search should try to fix, because some other blog softwares are also using content:encoded...

Best regards,
Garvin

[deminy]

Clear answer~~~~

What I can do is modifing the template file by myself, since Google won't fix that bug for us right now.

[garvinhicking]

Hi!

Yes, you could fix that for your readers, but as I mentioned it will have an impact on people with proper readers.

I am really sorry for that, but I hope you can understand the problem we're having there.

Maybe your google readers could just subscribe to your atom feed? Or you could relay your feed through feedburner?

Best regards,
Garvin

[gdanen]

This is not a bug of the RSS feed; "content:encoded" is properly valid according to RSS specs.

The problem is that s9y wants to show HTML content. However, the "<description>" field is by definition NOT allowed to hold HTML code.

So by using <description> we would either need to strip all HTML layout (which would suck) or we would be incompatible with the spec (which would suck). Thus we are using content:encoded, which allows it.

Hi Garvin,

Done some digging and found this link http://www.rssboard.org/rss-specificati ... elElements which shows <description> as a required element.

If you see other feeds such as http://rss.news.yahoo.com/rss/digitalimaging you will also see html in the <description> element.

Could an install/config option be made available that allows a user to choose whether to use <description> or <content:encoded>?

Thanks.

Gerry

[garvinhicking]

Hi!

[quteo]Done some digging and found this link http://www.rssboard.org/rss-specificati ... elElements which shows <description> as a required element.[/quote]

Yes, in the CHANNEL element it is required, but not inside the ITEM element.

If you see other feeds such as http://rss.news.yahoo.com/rss/digitalimaging you will also see html in the <description> element.

Yes, but putting HTML into there is not valid to first RSS 2.0 specs - and thus, some RSS readers would not properly interpret that.

Could an install/config option be made available that allows a user to choose whether to use <description> or <content:encoded>?

You could edit your feed*.tpl files to change that; adding a config option for this option is IMHO not required. Because, again, content:encoded does not impose any problem. It has worked perfectly sine the last 3 years in every RSS reader known to use.

Best regards,
Garvin

[gdanen]

You could edit your feed*.tpl files to change that; adding a config option for this option is IMHO not required. Because, again, content:encoded does not impose any problem. It has worked perfectly sine the last 3 years in every RSS reader known to use.

Thanks for pointing out the channel vs. item difference. I guess I am using a simplistic class to read the feed. (I am syndicating a feed from my son's blog on my site).

Do you know where I could find a class that will read the 2.0 feed properly, including the content:encoded?

Thanks

Gerry

[garvinhicking]

Hi!

AFAIK both MagpieRSS and Onyx support this! You might want to look at the serendipity sidebar plugin "Remote Feeds", which are able to parse foreign feeds...

HTH,
Garvin

[gdanen]

AFAIK both MagpieRSS and Onyx support this! You might want to look at the serendipity sidebar plugin "Remote Feeds", which are able to parse foreign feeds...

Thank you, Garvin.



Gerry