Hello, I wrote an my blog about the solution I have chosen perform what is describes. To put it in a nutshell I am using a middleware to direct the user to the language requested in the URL. I am not sure this follow any "Best Practice": http://yml-blog.blogspot.com/2007/12/django-internationalisation.html
May be this could help you. --yml On 20 déc, 00:32, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Dec 19, 2007 12:59 PM, Poromenos <[EMAIL PROTECTED]> wrote: > > > My application's UI depends on the set_language view being a link, and > > I don't think it should be up to the framework to force this on the > > developer. It would be better if the view supported both ways and the > > developer could choose whether they wanted functionality or spec > > compliance. This isn't a simple change, and it shouldn't be decided > > just like that... > > So write your own view which uses GET. Django encourages best > practices, and that includes following the recommendations of the HTTP > specification. You are free to throw down and trample the spec as much > as you like in your own code, but don't expect Django to help you with > it. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
