Wiadomość napisana w dniu 2009-08-13, o godz. 09:38, przez Enrico Sartorello:
> Nice information, so we can go ahead working with activate() :-) > > Let me ask you one more question: in your code, i see you're using > django.util.translation.get_language(), it's not a documented > function and according to django policies it can be changed or > removed in any new release. > Perhaps it's better using request.LANGUAGE_CODE? This function looks like part of public interface and the page http://docs.djangoproject.com/en/dev/misc/api-stability/ lists the whole internationalization subsystem as stable API so I'd not worry. get_language() gives you current language for the thread, which may be already different than request.LANGUAGE_CODE. -- Artificial intelligence stands no chance against natural stupidity Jarek Zgoda, R&D, Redefine jarek.zg...@redefine.pl --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
