WordPress and <content:encoded> vs <description>

Review the linked reallysimple and feedParserDemo packages, then compare their feed handling with the linked WordPress feed and RSS 2.0 specification. Done means reaching an explicit decision about how content:encoded and description should be handled, with the expected behavior documented for implementation.

I just typed this into ChatGPT.

I just noticed that the description element of an item in an RSS feed produced by WordPress doesn't contain style info but it is included in content:encoded. How am I just noticing that now? Do all feed readers understand this?

It said that it's a mixed bag of support. I honestly did not notice it until now when I was testing WordPress feeds in a context I had never looked at them closely in the past. I thought I was losing my mind! But I was correctly reading the situation.

I may have to change the code in FeedLand that handles this, and prioritize <content:encoded> if it's present?

I posted this publicly because I'm looking for some idea of how other developers of feed readers handle this.

The package that FeedLand uses to read feeds, it builds on the feedparser package.

What the RSS 2.0 spec says about it.

An example of a feed from my daveverse blog.