This is brilliant. Thank you so much Melvyn. Now I can switch the
cultures between British and US without having to change any code. :)
I was also surprised to see that Django is using by default the military
(24h) time. From what I remember the Americans usually prefer 12 hours
AM/PM.
So I have overridden it like '%I:%M %p', and it works 11:15 PM within
the forms.
Its just a bit odd that templates show 11:15 p.m. Slight difference in
the formatting. Also the dates within templates are defined like Aug
13, 2012. Doesn't confirm with my definition in formats.py.
Are they stored somewhere else?
On 13/08/12 15:30, Melvyn Sopacua wrote:
On 13-8-2012 16:16, houmie wrote:
But looking at this example, 'en/' is not good enough. British English
is also `en` but the date format is European. You know what I mean?
Again the culture seems to be forgotten :(
Unless I could define the path as en-GB/ and it would still be
recognized....
django/conf/locale/en_GB/ exists.
The internationalization modules first look for specific then for the
less specific match if it doesn't exist.
--
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 unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
