Hi Hejsan, we discussed this topic at the sprints of DjangoCon.eu some time ago. There is a page in the wiki for this topic where we summarized some ideas: http://code.djangoproject.com/wiki/ModelInterNationalization
Instead of one of the existing solutions (which all have serious drawbacks), I am in favor of approach number 4 on the wiki page: http://code.djangoproject.com/wiki/ModelInterNationalization#Multilingualmodelwithoneobjectperlanguage4 It avoids schema changes when a language is added and doesn't need JOINs for translating content. It also has drawbacks, but I would argue there are manageable. Please have a look at the proposal and it's API discussion. I agree with Jacob in that ModelTranslation will not be necessarily something for the Django core. We should rather identify issues or existing tickets which need to be resolved in order to go forward. The wiki page would be a good place to start collecting tickets (there's already one). Cheers Stefan -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
