I’ve given up waiting for Bloglines to fix their support for Atom 1.0 feeds with inline XHTML, so I’ve switched back to using a block of HTML code escaped using CDATA. Hopefully this will mean that it now displays correctly in Bloglines without the whitespace issue affecting it.
Update: Ooops, made a booboo 
. Should be fixed now. Honest…
Related Posts:
This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-ShareAlike 2.0 UK: England & Wales License.
November 11, 2005 at 13:01
Horribly broken in my bloglines – all html is there as text…..
November 11, 2005 at 13:04
Same here… looks awful I’m afraid :-\
November 11, 2005 at 13:32
I hate to say it, but it’s not working for me either.
November 11, 2005 at 16:15
Neil – I use bloglines. (sniffers)
November 11, 2005 at 17:34
Yeah, I’m getting the same problems as the others now – it just shows the plain HTML tag source, rather than the article. Personally, I prefered dealing with the whitespace, but it would be damned nice if Bloglines could fix it. Have you ever sent them a message?
November 11, 2005 at 18:42
That’s a little too escaped: CDATA *or* entity escaping will do the job, not CDATA *and*. But hoping for Bloglines to fix their Atom 1.0 problems, or other much more serious problems, is looking like a lost cause. They appear to have gone into no-maintenance mode.
November 11, 2005 at 20:04
Your Atom feed content is escaped using entities and CDATA. I think you need to pick just one.
Tim Bray’s Atom feed in Bloglines has been suffering from the whitespace issue forever, and it gets some embedded links wrong due to Bloglines not supporting xml:base, so I’m not holding my breath.
November 12, 2005 at 11:21
It works.
November 12, 2005 at 22:01
Better since the update — thanks!