Yes, I'd use the *_INPUT_FORMATS settings for this. The first format in the
list is how it will be displayed in the admin, though anything in the list
is acceptable. You _may_ need to turn off USE_L10N. not sure.
--
You received this message because you are subscribed to the Google Groups
"Dja
cs.djangoproject.com/en/dev/ref/settings/#std:setting-DATETIME_INPUT_FORMATS)
variable in `settings.py` untouched (i.e. default for the locale). Perhaps
this is the mistake?
As a general note, I've found the localisation documentation for Django to
be quite insufficient so I am totally happ
ORMAT.
>
> Is there any way around this? I can have sane datetime formats, but
> only if I disable all localisation?
>
> Cheers
>
> Tom
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussio
field, which I can add by disabling USE_L10N and defining an
> appropriate DATETIME_FORMAT.
>
> Is there any way around this? I can have sane datetime formats, but
> only if I disable all localisation?
>
> Cheers
>
> Tom
I should have just kept reading. I can create a cu
DATETIME_FORMAT.
Is there any way around this? I can have sane datetime formats, but
only if I disable all localisation?
Cheers
Tom
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegrou
Hello,
I was wondering if there any way to localise BDD test according to
project requirement is there any issue?
Sultan
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To
On Tue, Jan 18, 2011 at 11:40 AM, David Walker wrote:
> Thanks Lachlan.
>
> The middleware was the bit I was missing. The only mention of it on
> the Django website appears to be on the Middleware page. Perhaps it
> should go on the localisation pages?
There is a "How Djang
On Wed, Jan 19, 2011 at 01:40, David Walker wrote:
> There seem to be two main places where date formats originate. They
> are set in settings.py and in the locale's formats.py
> (django.conf.locale..formats).
>
> formats.py sets (amongst others) DATE_FORMAT and SHORT_DATE_FORMAT for
> the local
Thanks Lachlan.
The middleware was the bit I was missing. The only mention of it on
the Django website appears to be on the Middleware page. Perhaps it
should go on the localisation pages?
The middleware allows the pages to be localised to the browser's
locale, although there are st
On Sun, Jan 16, 2011 at 04:23, David Walker wrote:
> Despite reading round and round in circles in the documentation, I am
> completely baffled about localisation and how it works. I am not
> trying to do any translation yet, but want to code money and date
> formats right so that
Despite reading round and round in circles in the documentation, I am
completely baffled about localisation and how it works. I am not
trying to do any translation yet, but want to code money and date
formats right so that I don't have to rewrite things later.
It isn't even clear t
Thanks, for some reason en_GB works (but not en-gb) and I don't see a en_GB
stub under django/conf/locale. So it seems it works in a mysterious way
-Aaron
On Thu, Apr 22, 2010 at 12:24 PM, Ramiro Morales wrote:
> On Thu, Apr 22, 2010 at 3:48 PM, Aaron Lee wrote:
> > Hi,
> >
> > I am trying to
On Apr 22, 7:48 pm, Aaron Lee wrote:
> Hi,
>
> I am trying to create a UK version of my site and ran into some problems.
> I am manually setting my LANGUAGE_CODE to 'en-gb' and use
> django-admin.py makemessages -l en-gb and then run compilemessages
>
> For some reason it's not picking up the loca
On Thu, Apr 22, 2010 at 3:48 PM, Aaron Lee wrote:
> Hi,
>
> I am trying to create a UK version of my site and ran into some problems.
> I am manually setting my LANGUAGE_CODE to 'en-gb' and use
> django-admin.py makemessages -l en-gb and then run compilemessages
>
> For some reason it's not pickin
Hi,
I am trying to create a UK version of my site and ran into some problems.
I am manually setting my LANGUAGE_CODE to 'en-gb' and use
django-admin.py makemessages -l en-gb and then run compilemessages
For some reason it's not picking up the localised string, I am pretty sure
my setup is correct
Hi,
after moving server and upgrading the application this strange error
happens to me. Strange because it is inside Django - means nothing to
do with the app - and there wasn't changed anything with Django.
The only thing changed is that
'django.contrib.auth.backends.ModelBackend', has been ena
>I noticed that in this file you have long strings and which include
>lines like:
>comment" %}" />
Yeah, there is the problem that the make-messages.py can only pull
Python translations from .py files and can only pull translation tags
from raw templates, not from constructed templates. The solut
Thanks Ivan! I also had to export PYTHONPATH with my project's root dir
to make it work.
But in generated django.po there is no translation strings for file:
contrib/comments/templatetags/comments.py
I noticed that in this file you have long strings and which include
lines like:
(line 45 for e
cayco пишет:
Hi! I want to do polish translation for that file. I couldn' t find
anything to translate for that file in
conf/locale/en/LC_MESSAGES/django.po
What is the command to generato .po file for templatetags/*?
I tried:
/usr/lib/python2.4/site-packages/Django-0.91-py2.4.egg/django $ pyt
Hi! I want to do polish translation for that file. I couldn' t find
anything to translate for that file in
conf/locale/en/LC_MESSAGES/django.po
What is the command to generato .po file for templatetags/*?
I tried:
/usr/lib/python2.4/site-packages/Django-0.91-py2.4.egg/django $ python
bin/make-me
20 matches
Mail list logo
