Opened 13 years ago
Closed 13 years ago
#17670 closed Bug (fixed)
Incorrect SHORT_DATE_FORMAT and SHORT_DATE_TIME_FORMAT in Italian locale
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Internationalization | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
From the "Django internationalization and localization" group:
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.
Attachments (1)
Change History (3)
by , 13 years ago
Attachment: | fix_italian_default_date_formats.diff added |
---|
comment:1 by , 13 years ago
Component: | Uncategorized → Internationalization |
---|---|
Triage Stage: | Unreviewed → Ready for checkin |
Type: | Uncategorized → Bug |
Diff to fix Italian date formats