Okay I would like to jump in here quickly and give my two cents on this topic.
A very important distinction that should be made is the difference between 'dynamic' and 'static' translations. I call translations 'static' when they're strings that are fix in the templates (eg the text on the login button) as opposed to what I call dynamic, which are fields in the database. For the static translations we have a very good tool with gettext. This is a solid, mature and working tool that's used in a lot of places, not just Django. For dynamic translations we indeed have a huge problem, a problem I think needs to be solved. However this should not be done using 'backends' but rather by extending the ORM in a way that it allows applications like django-multilingual and the like to be written easier (without their own SQLCompiler, Query-class Queryset-class etc). Ideally Django would also provide a contrib app that actually gives you a full implementation of translatable database contents, but that's optional. Now the issue with this is, that it's not yet clear what needs to be done how in the ORM to make these kind of things easier. I have a couple of ideas and I'm sure others do too, but nothing mature has come up yet as far as I know. Jonas -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
