Use content:encoded instead of description when content:encoded is available

[mitchdowney]

https://stackoverflow.com/questions/7220670/difference-between-description-and-contentencoded-tags-in-rss2

[Inrumpo]

Checking different podcatchers, there seems to be some confusion weather to display the <description> or content:encoded. A recent bug in Apple Podcasts not displaying content:encoded anymore obviously didn't help. Since this has been fixed, afaik all major platforms do show content:encoded with some HTML tags allowed.

James Cridland has done a write-up concerning this topic. Though looking at the URL in your first post, I wouldn't support his advice to add HTML to the <description>.

Therefore: +1 for content:encoded, if available

---

Further: "description vs. content:encoded" doesn't seem to be the only source of confusion. What belongs into the <itunes:summary>? Who's showing the <itunes:subtitle>? Wouldn't this be a topic for the Podcasting 2.0 namespace to define and preserve those (or similar) tags and get rid of the confusion?

[mitchdowney]

This still seems like a good idea, but I just haven't had time to work on it / think about it :(

[Inrumpo]

It's not the most urgent one. I guess the chapter implementation is more important, since many users see this as a standard feature.