On 6/5/12 4:06 AM, Mo Mughrabi wrote:
I've been developing an application using Django for the past a year.
The application was written in a Debian environment, the development
and testing was entirely done in a debain machine.
Recently, I decided to move the application to my local Mac OS X
Thanks. I'll do so then.
>And those date hierarchy filters were displayed like they should be
>displayed. I mean translated. This was because date formatter uses
>strftime, which uses locale settings.
Yeah, but that only works with a single locale - many apps need
per-request locales, that's the r
n translated. This was because date formatter uses
strftime, which uses locale settings.
So it seems to me that Django's own datetime formatters could be
replaced with Python's own locale module
(http://www.python.org/doc/lib/module-locale.html), which would be good
thing for internati
On 2/8/06, TT <[EMAIL PROTECTED]> wrote:
> I found an interesting way to handle locales in admin's date_hierarchy
> feature. When day_lookup (GET-parameter 'variable'__day) is part of the
> request, the response uses django.utils.dates.MONTH in month's name,
> which uses gettext to translate month
Hello again. I didn't previously meant to be impolite. I'm quote new to
Django and I really like it.
But I was just wondering this implementation for time formatting. Seems
like this considers no one else but me or I posted this to wrong group.
I just wanted to ask if this really is the best way
I found an interesting way to handle locales in admin's date_hierarchy
feature. When day_lookup (GET-parameter 'variable'__day) is part of the
request, the response uses django.utils.dates.MONTH in month's name,
which uses gettext to translate month names, but other requests uses
Python's strftime
7 matches
Mail list logo
