[i18n_subsites] Allow merging the base settings with the translations settings.

[adiroiban]

To help organize the translations any text from pelicanconf.py that is presented on the site is put in a common dictionary

The idea is that if you add a new value in the default site and that site is not translated, it will be present in the translated site using the default language....similar to gettext.

---

Instead of using a simple copy with overwriting of root dict keys I went with a simple dict merge code.

I have simplified the tests.

to run the tests

virtualenv venv
. venv/bin/activate
pip install pelican
python -m unittest i18n_subsites/test_i18n_subsites.py

---

An example

L10N = {
    'author': 'Pro:Atria Team',
    'company': 'Pro:Atria Ltd',
    'company_number': '4213930',
    'product': 'SFTPPlus',
    'email': {
        'contact': '[email protected]',
        'sales': '[email protected]',
        'support': '[email protected]',
        },
    'menu': [
        # Text, URL, category.
        ('Product', '/product/', 'product'),
        ('Support', '/support/', 'support'),
        ('Contact', '/about/contact.html', 'contact'),
        ],
    }

I18N_SUBSITES = { 'de': 'L10N': {
    'company': 'Pro:Atria Ag',
    # The other emails are kept as in the main site.
    'email': {'sale': '[email protected]'},
    'menu': [
        # Text, URL, category.
        ('Produkt', '/de/product/', 'product'),
        ('Support', '/de/support/', 'support'),
        ('Kontakt', '/de/about/contact.html', 'contact'),
        ],
}}

[adiroiban]

I also have a patch to translate the values from pelicanconf.py using gettext.

But I think that this patch is still valid for people who don't want to use gettext

[georgkrause]

@adiroiban Mind filing the same against my fork at https://github.com/georgkrause/i18n_subsites ?