Internationalization.

Also-by: Servilio Afre Puentes <afrepues@mcmaster.ca>
Signed-off-by: Servilio Afre Puentes <afrepues@mcmaster.ca>
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.
!fixup Internationalization.
Add file ignore patterns for git
!fixup Buildout configurations for testing and development
No need for setting properties to default value
Use the localized format for the day
!fixup Internationalization.
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.
Minimal dependencies for i18n-extract to function
Don't override the site preference for the starting year
PEP8-guided clean-up

Also-by: UniCMS-Team <unicms-support@uni-koblenz-landau.de>