Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO@Stu: Thanks for your reply. Perhaps I wasn't so clear in my question - but I'm under no assumption that RSS == HTML. What I meant was that most of the "common" HTML formatting tags work fine (paragraphs, bolds etc.) when the block is enclosed within a CDATA declaration inside the RSS description tag. On the same lines, my idea is to dislpay embedded videos in the feeds in the exact location as it appears in the content. If I use enclosures, the video will appear as an attachment at the end of the feed and not within the flow of the content, making it somwhat contextually irrelevant. Cont...
      singulars
    2. CO...As for your queries, the reader may be any of the online / offline readers e.g. Google Reader, FeedReader, FeedDemon etc. But as you said, I don't think it'lll be possible to optimize the feed to render exactly the same across all readers. Still, I want it to render with the video wherever possible. I've come across feeds from several sites where content and videos appear intermittently. So there must be a way of doing so. As of now, W3C FeedValidator reports invalid placement of OBJECT tag within DESCRIPTION :(
      singulars
    3. COJust to give you some live examples, the following two links, when read through a feedreader appear exactly as they appear on the website, i.e. with the video embedded within the content: 1. http://gizmodo.com/5432254/weaponized-i+sobot-mini-humanoid-robot-tries-to-murder-your-other-toys 2. http://lifehacker.com/5430600/prep-for-the-holidays-with-diy-magic
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload