Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#28710 closed Bug (fixed)

Wrong Basque DATE_FORMAT string

Reported by: Claude Paroz Owned by: nobody
Component: Internationalization Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

Reported by Eneko Illarramendi on a Github pull request:
Basque DATE_FORMAT string is not properly escaped resulting in an Exception that breaks the Django i18n
module: The format for date objects may not contain time-related format specifiers (found 'e').

Change History (8)

comment:1 by Claude Paroz, 7 years ago

Has patch: set

comment:2 by Tim Graham, 7 years ago

Triage Stage: AcceptedReady for checkin

comment:3 by Claude Paroz <claude@…>, 7 years ago

Resolution: fixed
Status: newclosed

In 8c538871:

Fixed #28710 -- Fixed the Basque DATE_FORMAT string

Thanks Eneko Illarramendi for the report and initial patch.

comment:4 by Claude Paroz <claude@…>, 7 years ago

In 5595eccd:

[2.0.x] Fixed #28710 -- Fixed the Basque DATE_FORMAT string

Thanks Eneko Illarramendi for the report and initial patch.
Backport of 8c538871bda3832bca2dddefe317bf4a9230dd45 from master.

comment:5 by Claude Paroz <claude@…>, 7 years ago

In 50bbc93:

[1.11.x] Fixed #28710 -- Fixed the Basque DATE_FORMAT string

Thanks Eneko Illarramendi for the report and initial patch.
Backport of 8c538871bda3832bca2dddefe317bf4a9230dd45 from master.

comment:6 by Claude Paroz <claude@…>, 7 years ago

In c1fa667:

Refs #28710 -- Simplified l10n format test

comment:7 by Claude Paroz <claude@…>, 7 years ago

In 6481795d:

[2.0.x] Refs #28710 -- Simplified l10n format test

Backport of c1fa6672dd995e5ab4e06d5132db40ed0f41a47e from master.

comment:8 by Claude Paroz <claude@…>, 7 years ago

In 398a79ce:

[1.11.x] Refs #28710 -- Simplified l10n format test

Backport of c1fa6672dd995e5ab4e06d5132db40ed0f41a47e from master.

Note: See TracTickets for help on using tickets.
Back to Top