Up until 1.4.x Liferea had a simple implementation primarily using the Atom/RSS description. With the exception of the <content:encoded> tag from the Content-Namespace which depending on tag order will always overrule the default description. Only if there was no default item description additional namespace infos (atom:summary, dc:description...) where used as a content source.
This was an unsatisfactory solution for several reasons:
- More detailed infos in application specific namespaces are invisible.
- Ordering problems with <description> and <content:encoded> did sometimes hide better content.
- Dublin Core description (while rare to encounter) did never win.
- The scenario of a better summary than description always caused the short description to win.
As a result you might see additional content in namespace-rich feeds (e.g. iTunes podcast feeds).