WordPress and <content:encoded> vs <description>

未关闭
#320 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
wordpress
领域
backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
HTML
星标
134
派生
10
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

scripting/Scripting-News 的其他 Issue

查看 scripting/Scripting-News 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。