Internationalization

Also-by: Servilio Afre Puentes <afrepues@mcmaster.ca>
No need for setting properties to default value

Also-by: Servilio Afre Puentes <afrepues@mcmaster.ca>
Use the localized format for the day

Also-by: Servilio Afre Puentes <afrepues@mcmaster.ca>
Don't override the site preference for the starting year
Widget property values don't need i18n

It can actually lead to errors, as their values most probably would be
checked to literals with no internationalization.
Use the string directly as the i18n ID

No advantage for the translation, but it makes reading the code a bit
less easy. Also, for uniformity in the code, as the rest of the calls
to the MessageFactory are done without an ID.
Add file ignore patterns for git
Buildout configurations for testing and development

They are based on Plone 4.2, and the development buildout includes
tools for localization.

It is assumend that the buildout is run with a Python interpreter that
is isolated (e.g.: a virtualenv) to minimize the chance of version
conflict as Python and Zope libraries are extensively used for system
and desktop tools nowadays.
Minimal dependencies for i18n-extract to function
PEP8-guided clean-up

Also-by: UniCMS-Team <unicms-support@uni-koblenz-landau.de>
Gettext template file of translatable strings

Also-by: UniCMS-Team <unicms-support@uni-koblenz-landau.de>
Add German translation file
Git ignore pattern for Gettext binary message catalogue
Merge updated PO file into German translation file
Merge branch 'koblenz-i18n-v2'

Though the start of this branch was the i18n from the CMS team at
Koblenz-Landau, other commits round up the internationalization and
localization support, with some minor work in a couple of other areas.