It's now possible to specify an email address and an URI.

This was previously already possible by using the custom addElement function.

Add setContent() for Atom feed items

- Make it easy to get a <content> element on Atom entries
- Also spells "enclosure" correctly - "setEncloser" -> "setEnclosure"
- Fixes Atom test file on case-sensitive filesystems
- Tack a date_default_timezone_set() on tests, to avoid warnings

The namespace prefix and name can be set by invoking the addNamespace method of the Feed class.

See http://validator.w3.org/feed/docs/warning/MissingAtomSelfLink.html

It's actually the MIME type which is returned and then used for the HTTP Content-Type header field.

namespace FeedWriter

A minimal set of changes to support PSR-0-style autoloading:

- rename base class to \FeedWriter\Feed and FeedItem to \FeedWriter\Item
- break types out into \FeedWriter\ATOM, \FeedWriter\RSS1, and
  \FeedWriter\RSS2
- use class constants for versions
- make generateFeed() return a string rather than doing any IO itself
- add printFeed() to do output, if needed

My rationale for the last 2 items on that list is that our web framework
expects me to pass around strings, not do direct IO. I imagine needing
to grab the output and stash it in a variable or what-have-you is
a common use case, and it felt silly to have to wrap this in an
output buffer to accomplish that.

ATOM feed <author> element fix
Thanks for the fix!

The FeedWriter class is now abstract, which means it is not possible to directly create an instance of it. Use the new wrapper classes in FeedTypes.php instead. This also obsoletes the constructor's version parameter for end-users.

* Only accept instances of FeedItem
* Only accept instances of FeedItem with the same feed type

* Fixed spelling mistakes
* All \n's were replaced by PHP_EOL's

require_once -> require due to APC issues

APC shouldn't have to open files more than once, but it does if you use require_once instead of require. More details here:
http://www.techyouruniverse.com/software/php-performance-tip-require-versus-require_once

The minimal example should have minimal requirements...

This time using htmlspecialchars instead of htmlentities, because we need a encoding for XML, not for HTML.

So this has now not to be done by the user. Another benefit of this change: The examples do work now. ;-)