Oops, there were some remainings of an old edit that went unnoticed.

Especially changing the .ini-file parsing is more than a simple
bugfix.

Fix issue #23 
Thanks a lot, @dwcoder !

This commit fixes #23

Add the `string.strip()` function to the `get_config_dict()`, to remove
inverted commas around string values in the diceware.ini file.
The strip removes both `"` and `'`.
Add unit test to ensure the line:

    delimiter=" "

in the diceware.ini file is being parsed correctly as a space.

This helps to recognize options as such.

The removed vars were not really used in tests.

This way it is easier to check if any certain option is covered
already.

Try to cover all possibilities of `caps` related options when calling
`handle_options()`.

The modifications undone here, in
`test_handle_options_considers_configfile()` could have gone into an
own test. Each single test should only test a clear minimum of
things.

This specific test checked, whether configiles are considered at
all. It was not its purpose to examine correct interpretation of
keywords in the .ini-file; only to see whether these keyword values
can be changed at all.

If we wanted a complete and strict checking also of values, we had at
least to check all possible keywords, including 'randomsource' and
'wordlist'. Instead we only check a boolean, int, and string type
keyword.

Therefore the change to `test_handle_options_considers_configfile()`
should have gone to another test.

But then, the added testing is not neccessary. We had a test already
that should have checked the 'caps' value properly. This test was done
wrong before and is now done correctly, thanks to @dwcoder .

I therefore removed the added test functionality.

Running `pep8` or `flake8` over `tests/` complained about this one
blank line.

This commit fixes issue #21.
Change all occurences of the option `capitalize` to `caps` in
__init.py__.

Make the same change in the test_diceware.py.
Add a unit test that checks the output of main() after setting the
`caps = off` in the .diceware.ini.

This `Sphinx` theme is not a hard dependency of the `Sphinx` package
any more.

Add a common place where components can write messages to. Any
userinterface can decide, what messages should be visible
(depending on their severity).

With one item in sequence we do not have to roll dice. This holds for
all sorts of dice.

The moved comment was at the wrong place.

I guess it is obvious, how the first if-clause works.

We can simply do the (cheap) modulo operation after each die role.