I just submited my first stab at this. Please give it a try and let me
know what you think.
http://code.djangoproject.com/ticket/589
> what about dropping the "django_" part of the name? something like
> "../?locale=de" seems neatier to me... or maybe i18n_locale, if
> polluting namespace bother you...
I chosen django_language (not django_locale - we are only switching
languages, not locales currently ;-) ) because it's unlike
ciao (djangonauts™ ;) )
2005/10/3, Nebojša Đorđević - nesh <[EMAIL PROTECTED]>:
> Also in get_language_from_request I added support to set language via
> GET parameter and store that selection in the session or cookie, so
> you can set current locale (and store it) with .../?django_locale=de.
wha
> Great, but I want to have globally accessible language code (i.e. to
> select news based on current language), so I added method to get
> language to your Translation object and a helper function
> get_language to get current language. Also I added LANGUAGE_CODE and
> LANGUAGES to DjangoContext
On 3-09-2005, at 11:29, Nebojša Đorđević - nesh wrote:
Also I added LANGUAGE_CODE and LANGUAGES to DjangoContext
I'm forget to say that LANGUAGES will be in model choices format, i.e.:
LANGUAGES = (('en', 'English'), ('sr', 'Srpski'))
so I can use it as a choices for my models.
---
Nebojša
