WordPress and <content:encoded> vs <description>
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- wordpress
- Domain
- backend
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- HTML
- Stars
- 134
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/Scripting-News
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
scripting/Scripting-News#353 · 6 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
scripting/Scripting-News#332 · 25 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
scripting/Scripting-News#362 ·
-
Matt is moved aside Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
scripting/Scripting-News#361 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
scripting/Scripting-News#360 · 1 comment · 1 reaction ·
All issues in scripting/Scripting-News
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
good first issue refactor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100