From 4e0aa65d16e86cb426c49e33511bf013a47c4fbb Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Wed, 28 Apr 2010 11:27:38 +0000 Subject: Refs #13339 -- Disable %b/%B-based locale datetime input formats, and document that they are problematic. git-svn-id: http://code.djangoproject.com/svn/django/trunk@13039 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/i18n/localization.txt | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/topics/i18n/localization.txt b/docs/topics/i18n/localization.txt index 8e1beaef46..91c771f610 100644 --- a/docs/topics/i18n/localization.txt +++ b/docs/topics/i18n/localization.txt @@ -265,8 +265,14 @@ current locale. Django will also use localized formats when parsing data in forms. That means Django uses different formats for different locales when guessing the format -used by the user when inputting data on forms. Note that Django uses different -formats for displaying data, and for parsing it. +used by the user when inputting data on forms. + +.. note:: + Django uses different formats for displaying data to those it uses for + parsing data. Most notably, the formats for parsing dates can't use the + ``%a`` (abbreviated weekday name), ``%A`` (full weekday name), + ``%b`` (abbreviated month name), ``%B`` (full month name), + or ``%p`` (AM/PM). To enable a form field to localize input and output data simply use its ``localize`` argument:: -- cgit v1.3