bump version number and update company info
Restore compatibility with narrow builds of Python.

You know how narrow builds are designed to replace astral characters
with two surrogate characters and hope you don't notice? Regular
expressions notice. Narrow builds turn them into different expressions
that are completely wrong.

Fortunately, in this case, it was so wrong that it prevented the module
from being imported.
version 3.0.3
Correct Cyrillic characters less aggressively. Fixes #13.
2.6 compatibility.
Merge pull request #15 from adriaant/master

Merging adriaant's change to restore 2.6 compatibility. Thanks!
v3.0.4 - restores python 2.6 compatibility
fix_file was using totally the wrong arguments. Fixed that.
Version 3.0.5
Document and clean up the character map building process
Document the case where we give up on decoding text as Windows-1252.

This includes fixing an inaccurate comment that appeared after it.
fix_entities can now be True, False, or 'auto'
Make sure to run build_data in Python 3.3 or later.
Add tests for the fix_entities parameter
Version 3.0.6
let test_unicode be used as a script for profiling
Add "bad codecs" for decoding bad bytes.

Simply by using a statement such as "import ftfy.bad_codecs", you will be able
to decode popular, messy encodings that Python is too dignified to support,
such as 'sloppy-windows-1252' and 'cesu-8'.
Simplify how sloppy codecs are built
allow sloppy codecs to be cached
fix expected output in 'plan_so_far'