Thanks for your reply Ulrich. If I set the locale in WSGI would that persist for all connections? If so that sounds like the best option.
Thanks Jay On Tuesday, September 16, 2014, <rettevhci...@googlemail.com> wrote: > Hi, > I ran into a similar problem yesterday while programming a web shop with > Django (Version 1.6, Python version 3.3) where language switching should > immediately have an effect on the way prices, etc. are displayed (doing so > by a <form action="/i18n/setlang/" method="POST" > in the template and > redirecting back to the page where it was called). The locale is indeed not > set this way and needs to be set explicitly. What I finally came up with as > a first working solution as part of a function: > > def convert_my_price(_price) # _price is a decimal.Decimal > language = django.utils.translation.get_language() > if language == 'en': > locale.setlocale(locale.LC_ALL, 'en_US.utf-8') # 'en_GB.utf-8' > didn't work for me > else: > locale.setlocale(locale.LC_ALL, 'de_DE.utf-8') # this is the > fallback > > _loc = locale.localeconv() > . > . # process the Decimal > . > return my_price_as_a_string > > After doing so I have access to the locale details stored in the > dictionairy _loc, like e.g. _loc['thousands_sep'], _loc['currency_symbol'] > in this function, but also everywhere else via locale.localeconv() > This function however is currently called from within class based views, > but also implemented as a template filter. Of course one should not set the > locale every time when calling this function, as you mentioned > locale.getlocale() will should whether it was correctly set or not. > > Where you call locale.setlocale depends on your application. When you only > have to set it once maybe the best would be to call it in even in e.g. > wsgi.py > > Best regards, > Ulrich > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-users/9kuQBMknp9g/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com > <javascript:_e(%7B%7D,'cvml','django-users%2bunsubscr...@googlegroups.com');> > . > To post to this group, send email to django-users@googlegroups.com > <javascript:_e(%7B%7D,'cvml','django-users@googlegroups.com');>. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/65e039ab-b2ef-4f78-ab39-0ee53f2f5629%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/65e039ab-b2ef-4f78-ab39-0ee53f2f5629%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- a: 1 Oak Cottage, Town Lane, Mobberley, WA16 7HJ t: 01565 873 019 | 07899 872 306 e: ja...@hargreaves.me.uk -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAKceJevwa3u7GRdhX%3DBPOjg_FEWyQEVOvbvAW3a23dM6Ziqezg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
