Wrong date input format for Brazilian localization

[Aymeric Augustin]

Basically, this patch means that %Y-%m-%d will no longer be accepted in submitted forms. This is backwards incompatible: some people may rely on this format being accepted, for instance if they use calendar widgets in Javascript that produce such a value. I don't think %Y-%m-%d is ambiguous in any language, so it can't hurt to keep it.

For this reason, I vote -1, but I'd like another opinion before rejecting the patch.

[Guilherme Gondim]

Instead take it out we can just change the order. I see many persons writing yours own format.py to use the Brazilian standard.

[Aymeric Augustin]

Yes, that's a good idea.

The first item in DATE_INPUT_FORMATS is used to display the current value in form fields when the field has no format attribute. If I understand correctly, this is why you want to change DATE_INPUT_FORMATS. Re-ordering the formats resolves this issue without affecting form submission.

Can you submit a new patch?

[Guilherme Gondim]

Yep, I wish change just to show the date in the correct standard. Doesn't make sense take out %Y-%m-%d... :-D

I will submit the new patch asap.

[Guilherme Gondim]

Better one.

[Guilherme Gondim]

New patch attached, thank you! :-)

[anonymous]

Those patches are still incomplete. DATE_FORMAT and DATETIME_FORMAT remain incorrect. They should use "F", instead of "N", for month names,

DATE_FORMAT = r'j \de F \de Y'
DATETIME_FORMAT = r'j \de F \de Y à\s H:i'

See ​http://en.wikipedia.org/wiki/Date_and_time_notation_in_Brazil. Also see django.conf.locale.pt.formats, the European Portuguese module, which already use those formats. In Brazil, month names are not abbreviated.

[Claude Paroz]

Same with DATE_FORMAT/DATETIME_FORMAT also fixed

[Jannis Leidel]

In [16724]:

Fixed #16349 -- Fixed Brazilian localization formats. Thanks, Claude Paroz, semente and Guiljerme Gondim.