Hi all,
I've noticed an inconsistency in the `it` locale formats.py file
(django/conf/locale/it/formats.py) both in Django 1.3.1 and trunk.
The file contains:
SHORT_DATE_FORMAT = 'd/M/Y' # 25/12/2009
....
DATE_INPUT_FORMATS = (
'%d/%m/%Y', '%Y/%m/%d', # '25/10/2006', '2008/10/25'
'%d-%m-%Y', '%Y-%m-%d', # '25-10-2006', '2008-10-25'
'%d-%m-%y', '%d/%m/%y', # '25-10-06', '25/10/06'
)
1) The SHORT_DATE_FORMAT format listed does not match the comment (note
the 'M' in the format - this should be 'm' for a numerical month)
2) The listed SHORT_DATE_FORMAT is not one of the accepted
DATE_INPUT_FORMATS
Point 1 could easily be a typo, but point 2 is a bit more serious. It means
that if you use SHORT_DATE_FORMAT to format the default date in a form,
then that default does not pass validation when the form is submitted.
For example, today's date as output by SHORT_DATE_FORMAT is '10/Feb/2012'.
If this is used as the default value for a form field, then that form field
will fail validation.
Is this desired behaviour? Shall I raise a bug?
--Craig Blaszczyk
--
You received this message because you are subscribed to the Google Groups
"Django internationalization and localization" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-i18n/-/0Jl1cuVGgoAJ.
To post to this group, send email to django-i18n@googlegroups.com.
To unsubscribe from this group, send email to
django-i18n+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-i18n?hl=en.
