On 11/7/06, Bill de hOra <[EMAIL PROTECTED]> wrote: > There's no direct support for this kind of thing in the core (that's > afaik, I haven't been following the trunk in the last couple of months). > And, if there's no standard patterns or models for this, is this worth > thinking about at as an extension app? In my part of the world, being > able to run a multilingual site is often a 'checkbox' requirement.
You're right that there's currently nothing built in to Django which would cover this, but it would definitely be a great thing to add; I'm not sure what the best way to genericize it would be, though; most of the models I end up with whenever I think about this problem end up being more complicated than they probably need to be (e.g., I generally conceive of a base model which holds the core metadata of the object, and then translated versions related to it, with a whole scheme of access methods on the base to figure out which languages are available and fetch them, etc. etc.). I don't have any real experience in that area, though; what are some general best practices for the backend design of a multilingual site? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
