Added the missing LANGUAGES bit to settings.py and it works!
Added:
English
Nederlands
to the template.
Method in views.py is:
def customer_welcome(request):
return render_to_response('customer_welcome.html',
'request':request, 'user':request.user})
And i18n sorts it all out!
Thank
Gribbie wrote:
> Soory - that should read "...when I got to the next screen the selected
> language is lost and so the page is in English"
Check your settings.py:
MIDDLEWARE_CLASSES = (
"django.middleware.common.CommonMiddleware",
"django.contrib.sessions.middleware.SessionMiddleware",
Soory - that should read "...when I got to the next screen the selected
language is lost and so the page is in English"
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
I've now got Nederlands in my
template - clicking on it translates into Dutch which is great BUT when
I go to the next screen the language option is lost :-(
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django d
I do have {% load i18n %} in my template already - will try your
function tomorrow, it's home time now :-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
Gribbie wrote:
> I've got a click the flag on the welcome screen - when they 1st load
> the page it is in english - it uses the last 2 lines of the method:
>
> request.session['django_language']='en-uk'
> return render_to_response('welcome.html', {'request':request,
> 'user':request.u
If I display {{request.sesssion.django_language}} on my template it is
"en-uk" on 1st load which is correct. I then click the french flag
which passes lang='fr' and...
If I use HttpResponseRedirect then the page is translated but
{{request.sesssion.django_language}} is still 'en-uk'.
If I use r
Hiya
I've got a click the flag on the welcome screen - when they 1st load
the page it is in english - it uses the last 2 lines of the method:
request.session['django_language']='en-uk'
return render_to_response('welcome.html', {'request':request,
'user':request.user})
If they click
Gribbie wrote:
> Hi Nebojsa
>
> Thanks for your reply - we are using django internationalisation. It
> all works fine when logged in it's just the introduction pages before
> the user logs in where we have the problem.
Well, if django i18n engine can't find out proffered locale from the browse
Hi Nebojsa
Thanks for your reply - we are using django internationalisation. It
all works fine when logged in it's just the introduction pages before
the user logs in where we have the problem.
Many thanks
Gribbie
--~--~-~--~~~---~--~~
You received this message
Gribbie wrote:
> Hi
>
> I have an application which when the user is logged in translates
> using:
> request.session['django_language']='en-uk' or what ever language
> code they select.
>
> This works fine when the user is logged in but I'd like to offer the
> user the option to translate th
Hi
I have an application which when the user is logged in translates
using:
request.session['django_language']='en-uk' or what ever language
code they select.
This works fine when the user is logged in but I'd like to offer the
user the option to translate the "welcome" screen. I've done th
12 matches
Mail list logo
