A dictionary with details about the entry title.
Comes from
- /atom:feed/atom:entry/atom:title
- /rss/channel/item/title
- /rss/channel/item/dc:title
- /rdf:RDF/rdf:item/rdf:title
- /rdf:RDF/rdf:item/dc:title
See also
Same as entries[i].title.
If this contains HTML or XHTML, it is sanitized by default.
The content type of the entry title.
Most likely values for type:
- text/plain
- text/html
- application/xhtml+xml
For Atom feeds, the content type is taken from the type attribute, which defaults to text/plain if not specified. For RSS feeds, the content type is auto-determined by inspecting the content, and defaults to text/html. Note that this may cause silent data loss if the value contains plain text with angle brackets. There is nothing I can do about this problem; it is a limitation of RSS.
Future enhancement: some versions of RSS clearly specify that certain values default to text/plain, and Universal Feed Parser should respect this, but it doesn't yet.
The language of the entry title.
language is supposed to be a language code, as specified by RFC 3066, but publishers have been known to publish random values like “English” or “German”. Universal Feed Parser does not do any parsing or normalization of language codes.
language may come from the element's xml:lang attribute, or it may inherit from a parent element's xml:lang. If the feed does not specify a language, language will be None, the Python null value.
The original escaping mode used to encode the entry title.
Possible values:
- escaped
- xml
- base64
mode is only useful in rare situations and can usually be ignored. It is the original escaping mode that the feed used to encode the value. By the time you see it, Universal Feed Parser has already unescaped the value properly. Clients should never need to manually unescape values.
The original base URI for links within the entry title.
base is only useful in rare situations and can usually be ignored. It is the original base URI for this value, as specified by the element's xml:base attribute, or a parent element's xml:base, or the URI of the feed. (This behavior is spelled out in the XML Base specification.) By the time you see it, Universal Feed Parser has already resolved relative links in all values where it makes sense to do so. Clients should never need to manually resolve relative links.