I'd like to show you my approach, which I use for one of my clients. For every model that needs to have multi-lingual content, you add two fields: a "language" and a "translation_of" field.
Objects are created in a default language (altough this is not required). To translate an object, you create a new page and set the translation_of field to the object in the default language that you are translating. A set of helper methods allow you to get the root version of the object (in the default language), all translations of an object, or a specific translation. These are useful for adding translation links. Here is the code: http://www.bigbold.com/snippets/posts/show/2979 Note again that it's perfectly fine to add objects in another language than the default that don't have translations in the default language. One restriction: you cannot translate a page that doesn't have a default language version. Frederik --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
