#6460: New feature : Multilingual Content
-------------------------------------------+--------------------------------
Reporter: g00fy | Owner: nobody
Status: new | Milestone:
Component: Internationalization | Version:
Resolution: | Keywords: multilingual
content i18n-rf
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by tomgruner):
It seems like for complex models you can use django-multilingual-model
http://code.google.com/p/django-multilingual-model/
This is not the same as django-multilingual. It´s much simpler.
You have to create the translation models yourself, but it is very easy to
use and doesn´t limit the model complexity in any way as it not trying to
be overly magical.
By not moving multilingual fields into the core, I think Django can remain
flexible to different multilingual solutions, as it´s hard to come up with
a one size fits all solution. I´ve developed an app with django-
multilingual-model and have had no problems, since it´s based on the
normal ways models are related in Django anyway. I am just a user of
django, not on the dev team, but I would prefer django as is with respect
to multilingual content.
Also you can see a list of current solutions here:
http://and-other-things.blogspot.com/2009/04/list-of-django-multilingual-
model.html
--
Ticket URL: <http://code.djangoproject.com/ticket/6460#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
