I had more or less the same situation to solve and I think http://www.djangosnippets.org/snippets/371/ should come quite close :-)
2007/9/21, erik <[EMAIL PROTECTED]>: > > > Me, too, I stumbled over this change lately. > > My understanding of the HTTP spec is that there shouldn't be > different content for a given URL without having to use a POST > request. The solution for our problem (having links to switch > languages) might be to use unique URLs for each translation, like > > /en/startpage/ > /zh-cn/startpage/ > > I didn't think about the required i18n-logic to have this automated, > so in the meantime I just use the old set_language funtionality in a > custom function. > > best > -- erik > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
