The Blogger API is the Atom API with an addition for <a href="http://code.blogger.com/archives/atom-docs.html#extensions">converting line breaks</a>. So all the Blogger API clients *are* Atom API clients.<br><br><div><span class="gmail_quote">
On 7/8/06, <b class="gmail_sendername">Gabor Hojtsy</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sat, 8 Jul 2006, Karoly Negyesi wrote:<br>>> * We don't ship many other things that are very typical for blog<br>>> installations, like a wysiwig editor, urlfilter.module, or<br>>> Atom support.<br>>
<br>> As I have just written a blog API client module, I can tell that the world is<br>> rushing towards Atom. So, providing an ancient API server is not bad, but not<br>> core worthy any more.<br><br>Think about the other end, the clients connecting to this blogger API
<br>server. There are a multitude of blogger API / metaweblog API /<br>movabletype API clients. What about *Atom API* clients? Note to those<br>quick reading, Atom API is not the Atom syndication format, but the<br>publishing protocol.