Multilanguage - I know what I want, should I do it this way?

Hi, I'm currently working on a simple CMS that needs to be multilanguage. I've read through all the posts on the list and came up with this simple solution. My use scenario is like this: * translations are per model (not per field) * language selection is per request (saved in a cookie or so) I

Re: Multilanguage - I know what I want, should I do it this way?

> Look at this:http://code.google.com/p/django-multilingual/ I dont want to use that, because it is basically unmantained - what it does is very nice and if I were sure this works with django 1.0 and such I would use it. Also I dont want to re-write D-M because it does a lot of things I dont need

Re: Multilanguage - I know what I want, should I do it this way?

> You could use the number like you would like to use your id. The id- > column itself is of course still added by django as the pk. I see. Thank you for all the replies, I will use the unique_together solution. --~--~-~--~~~---~--~~ You received this message bec