Load a default-named configuration file if present
Removing utils.file_exists and replacing with os.path.isfile
Adding information to argparse help
Fixing help text
Add non unique slug warnings for translations
Check URL overwrite. Fixes #446.

Check that template-generated files don't overwrite each other. Log a critical
message otherwise, and exit with non-zero status.
Import wordpress pages to pages/ subdir with --dir-page option

When importing from Wordpress, the --dir-page directive (disabled by
default) automatically adds files to the pages/ when they are recognised
as pages, as opposed to posts.
Add `DOCUTILS_SETTINGS` to allow to customize the docutils Publisher.
Fixes #708 SUMMARY_MAX_LENGTH=0 should return empty string
Merge pull request #867 from avaris/summary-max-length

Fixes #708 SUMMARY_MAX_LENGTH=0 should return empty string
Add warning to docs re: DELETE_OUTPUT_DIRECTORY
Make tags and cats case insensitive. Fixes #704.

More precisely, group tags or categories without considering the case.
This fixes the bug where two categories with just the case as difference were
considered as distinct, but generate the same file: one overwriting the other.

Thanks to @Avaris for helping with the tests.
Merge pull request #845 from Rogdham/case-insensitive_caterogy_tag

Make tags and cats case insensitive. Fixes #704.
Handle critical exception logging correctly in localized systems

Python generates certain exception messages (like IOError) in system
language, if locale is set. This ensures that the message is properly
converted to unicode in Python 2.
Merge pull request #874 from avaris/non-ascii-error

Handle critical exception logging correctly in localized systems
Add reST example to arbitrary metadata FAQ entry
Add more detail to Pygments FAQ entry. Fixes #821
use string find() instead of index().  Fixes #880.

We're expecting a non-match to return -1, which is what find() does,
but index() instead throws a ValueError.
Update importer documentation

Dependencies were not the good one, wordpress importer needs BeautifulSoup4 and lxml
Markdown summary should not include content footnote

Markdown instance carries state for subsequent uses. Content
and summary parsing is done with the same instance. Since
footnotes are processed with an extension and stored as state,
content footnote is duplicated for summary.

This PR adds a ``.reset()`` call before summary parsing to clear
the state. It also adds a test case with footnotes.