Avoid inserting translation fields into forms as extra fields, TranslationAdmin handles them properly on its own.
New ``update_generated_fields`` command (currently resaving all models deriving from Slugged, MetaData and Page).
In case of some fields (such as "slug"), one cannot have one translation set and rely on fallbacks for other languages, as they don't work with filtering / lookups.
For example, if you create a new project loading example fixtures, sync and update translation fields, you still won't be able to browse most pages in any non-default language until you give them a chance to generate translated slugs.
Make editable fields on lists shorter. Grappelli-safe fixes vTextField width to 692px, this is too much for Cartridge discount codes list and products options list with translations.
Keywords translation. Assignments are intended to be the same for every language, thus only Keyword.title and keywords_string (on concrete subclasses of MetaData) are made translatable, with the latter recomputed on change for all languages as with other derived attributes.
Page admin only allows entering keywords in the active language (there doesn't seem to be any sensible way to inline translations), so KeywordAdmin is exposed separately to make it possible to translate keywords.
Merge branch 'feature/modeltranslation-integration' into develop

Conflicts:
	mezzanine/pages/admin.py
Run makemessages for all apps, as some translatable strings are missing from .po-s. Unfortunatelly there doesn't seem to be any way to tell the command to preserve wrapping.
Filled new strings and did some corrections in the core app.
Merge branch 'feature/polish-translation-update' into develop