Incorrect SHORT_DATE_FORMAT and SHORT_DATE_TIME_FORMAT in Italian locale
|Reported by:||masterjakul@…||Owned by:||nobody|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
From the "Django internationalization and localization" group:
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.
Change History (3)
Changed 5 years ago by masterjakul@…
comment:1 Changed 5 years ago by jezdez
- Component changed from Uncategorized to Internationalization
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Ready for checkin
- Type changed from Uncategorized to Bug