Using locales 'en-au' 'en-ca' 'en-nz' and 'en-za' in Django

Hi, Django has en and en-gb installed as languages in it's core. If a django project wishes to use other locales such as 'en-au' or any of the others listed in the subject line, how would one go about this given that a language cannot be used unless it is in the core? Essentially, how does one

Re: Django, multiple domains, multiple locales/languages

This could solve your problem domain based accounts. http://github.com/CrowdSense/django-muaccounts/tree/master On Jul 24, 3:57 pm, Joshua Russo wrote: > I ran into some conceptual problems with lazy vs non-lazy too. Any global > context needs to be lazy. This includes

Re: Django, multiple domains, multiple locales/languages

I ran into some conceptual problems with lazy vs non-lazy too. Any global context needs to be lazy. This includes everything declared outside of any function or class context and the class instance variable declarations (tho not the declarations made in __init__ or __new__ of a class) On Fri, Jul

Re: Django, multiple domains, multiple locales/languages

OK, thanks for suggestion - however it seems the problem was somewhere else - I was using ugettext where ugettext_lazy was supposed to be used (ex. in forms.py). The documentation should be more clear that the choice between ugettext and ugettext_lazy is quite important and may lead to strange

Django, multiple domains, multiple locales/languages

Hi, I have a problem with Django - I'm trying to build a website which will work on a couple of different domains and each domain should have a different language/locale. Example: domain.com -> English domain2.pl -> Polish The SITE_ID should change accordingly when I visit the corresponding

Re: Format dates using a specific locales under mod_python

Wiadomość napisana w dniu 2009-05-29, o godz. 03:42, przez luper rouch: >>> I tried to put locale.setlocale(locale.LC_TIME, 'fr_FR.UTF-8') in >>> the >>> settings file and it works well on the development server. The >>> problem >>> is under mod_python dates are printed in the selected

Re: Format dates using a specific locales under mod_python

2009/5/29 Graham Dumpleton : > > > > On May 28, 10:16 pm, luper rouch wrote: >> By default, dates are formated in English (things like .strftime("%A") >> return days names in English). >> >> I tried to put locale.setlocale(locale.LC_TIME,

Re: Format dates using a specific locales under mod_python

On May 28, 10:16 pm, luper rouch wrote: > By default, dates are formated in English (things like .strftime("%A") > return days names in English). > > I tried to put locale.setlocale(locale.LC_TIME, 'fr_FR.UTF-8') in the > settings file and it works well on the

Format dates using a specific locales under mod_python

By default, dates are formated in English (things like .strftime("%A") return days names in English). I tried to put locale.setlocale(locale.LC_TIME, 'fr_FR.UTF-8') in the settings file and it works well on the development server. The problem is under mod_python dates are printed in the selected

Re: Locales

On May 22, 4:48 pm, Gabriel wrote: > Actually LANG is an example ;) > The real directory structure is: > > locale/fr/LC_MESSAGES > locale/es/LC_MESSAGES > locale/de/LC_MESSAGES > and so on > > Regards. I got that :) so you have already used lowercased LANG directory

Re: Locales

V escribió: > my first guess would be to try > > locale/lang/LC_MESSAGES > instead of > locale/LANG/LC_MESSAGES > > I hope this helps! > > Have a nice day, V > Actually LANG is an example ;) The real directory structure is: locale/fr/LC_MESSAGES locale/es/LC_MESSAGES locale/de/LC_MESSAGES

Re: Locales

my first guess would be to try locale/lang/LC_MESSAGES instead of locale/LANG/LC_MESSAGES I hope this helps! Have a nice day, V On May 21, 10:42 pm, "Gabriel ." <gabriel@gmail.com> wrote: > Hi all, > > I've generated and compiled the locales, under my app path,

Locales

Hi all, I've generated and compiled the locales, under my app path, locale/LANG/LC_MESSAGES (django.mo and the .po of course) When I select the language, some of the strings appears translated (the ones shared with django), but no the strings on the django.mo file (the one I created

Re: Problem routing to certain i18n locales/languages

On Mon, 2009-03-02 at 11:24 -0800, Scott wrote: > Hi Malcolm, > > Thanks for your response, I suspected that it was something similar. > I'm actually using the Django helper for App Engine (http:// > code.google.com/p/google-app-engine-django/), so there is no django > installation to configure.

Re: Problem routing to certain i18n locales/languages

Hi Malcolm, Thanks for your response, I suspected that it was something similar. I'm actually using the Django helper for App Engine (http:// code.google.com/p/google-app-engine-django/), so there is no django installation to configure. Further to this, all of the strings are being provided by

Re: Problem routing to certain i18n locales/languages

On Fri, 2009-02-27 at 13:15 -0800, Scott wrote: > Hello, > > I'm working on an App Engine (using the Django helper) application > that is to be presented in a number of different languages, and > routing is managed primarily by cookie. The app is serving the correct > pages in most cases, but a

Problem routing to certain i18n locales/languages

Hello, I'm working on an App Engine (using the Django helper) application that is to be presented in a number of different languages, and routing is managed primarily by cookie. The app is serving the correct pages in most cases, but a few languages default back to English, despite the cookie