2010-06-15 10:07:36 +00:00
|
|
|
Metadata-Version: 1.0
|
|
|
|
|
Name: django-modeltranslation
|
2019-02-12 22:05:28 +00:00
|
|
|
Version: 0.13-beta2
|
2010-06-15 10:07:36 +00:00
|
|
|
Summary: Translates Django models using a registration approach.
|
2012-10-17 13:53:39 +00:00
|
|
|
Home-page: https://github.com/deschler/django-modeltranslation
|
2010-06-15 10:07:36 +00:00
|
|
|
Author: Peter Eschler,
|
2014-01-04 23:44:23 +00:00
|
|
|
Dirk Eschler,
|
|
|
|
|
Jacek Tomaszewski
|
2012-10-17 13:53:39 +00:00
|
|
|
Author-email: "Peter Eschler" <peschler@gmail.com>,
|
2014-01-04 23:44:23 +00:00
|
|
|
"Dirk Eschler" <eschler@gmail.com>,
|
|
|
|
|
"Jacek Tomaszewski" <jacek.tomek@gmail.com>
|
2010-06-15 10:07:36 +00:00
|
|
|
License: New BSD
|
|
|
|
|
Description: The modeltranslation application can be used to translate dynamic
|
2012-10-17 13:53:39 +00:00
|
|
|
content of existing Django models to an arbitrary number of
|
|
|
|
|
languages without having to change the original model classes. It
|
|
|
|
|
uses a registration approach (comparable to Django's admin app) to
|
|
|
|
|
be able to add translations to existing or new projects and is
|
|
|
|
|
fully integrated into the Django admin backend.
|
2010-06-15 10:07:36 +00:00
|
|
|
|
|
|
|
|
The advantage of a registration approach is the ability to add
|
|
|
|
|
translations to models on a per-project basis. You can use the
|
|
|
|
|
same app in different projects, may they use translations or not,
|
|
|
|
|
and you never have to touch the original model class.
|
|
|
|
|
Platform: UNKNOWN
|
|
|
|
|
Keywords: django translation i18n
|
