Updated README.md

Added a blurb about using the `STDIN` filename and also the new syntax for the
`comment` option.
Now support EXCERPT keyword in Header

Have added support for creating an excerpt for a blog post, which necessitated
the addition of the EXCERPT keyword for headers.  To more fully support what the
excerpt in the header, I've provided for python-style docstring quoting.  These
strings are delimited by a sequence of triple double-quotes, like the docstrings
in python code.  In addition to allowing for any character within the quotes,
these strings can span multiple lines.

The version has been bumped to 1.1.1 in __version__.py.

Support for getting the excerpt is also supported in the "getPost" option as
well as when converting a header object into a string.
Updated README.md

Added the EXCERPT keyword to the README.md file.
Updated Online Documentation

Added the EXCERPT keyword and explanation of quoted strings to the
documentation.
Further Documentation Mods

Fixed formatting issued in README.md for EXCERPT.

Slightly modified description strings in the setup.py file.
Modified Long Description

In the long description, I've added a link to the project source on github.
This will show up on the pypi package page.
Code Cleanup

Tried to make code function commenting and documentation consistent across all
modules.  This doesn't mean all functions or methods are documented, just that
all are done so the same way.

Also, made several code name modifications for consistency purposes and, within
modules, changed function or method names to disambiguate their actual purpose.
Fixed Header __str__ Method

Actually, there was nothing wrong with the method per say.  The problem was that
we modified the header string when processing the header categories in
fileprocessor.py.  That processing removed information that was extraneous for
WP blog software, but useful for blogtool.  Now a separate category list is
generated  and returned for use with posting.

Also, now raise FileProcessorErrors where before we just quit.
Added Ability to Supply Custom More Text

By default, for posts that have part of their content hidden, WP displays a MORE
link at the bottom of the post.  This text can be customized by modifying the
HTML comment that generates the MORE link.  Simply add the custom text right
afte the 'more' in the HTML comment like so:  `<--more Custom More Text-->`.

This is now supported by detecting a single line in the post file that starts
with at least 3 '+' characters, which can be space separated.  If no text is
supplied afterwards, then the standard 'MORE' link is generated.  Any text that
does follow the '+' characters is then used as the text in the 'MORE' link.  Any
trailing '+' characters are ignored.

When getting the post from the blog, the `wp_more_text` field is now checked and
an appropriate line is generated for the post file using the new '+' character
notation.

The old `### MORE ###` is still supported for historical reasons.
Updated Documenation for V1.1.2

Release commit for version 1.1.2, with all documentation updates made.
Merge branch 'master' into dev

Bring in all the updated features from the master branch.
Merge Broke Get Post Option

Had to update the xmlrpc `getPost` method to request the `post_excerpt` so that
processing the downloaded post could be properly completed.