Django

Code

Ticket #2063 (closed: fixed)

Opened 2 years ago

Last modified 1 year ago

[patch] make date_hierarchy Admin feature fully i18n-able

Reported by: ramiro Assigned to: adrian
Milestone: Component: Admin interface
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

This patch modifies the code that generates the date hierarchy of the automatic Django admin interface by fully using Django i18n services instead of datetime.stftime().

This patch depends on the patch attached to #2062 and provides an alternate implementation to the one proposed in #1749. The difference is that this one provides for full internationalization by using format specifiers documented by http://www.djangoproject.com/documentation/templates/#now and so not hard-coding the order of the fields (e.g. in Spanish a month+day date spec like "January 1" reads "1 Enero").

Regards,

Attachments

date_hierarchy_i18n.diff (2.6 kB) - added by ramiro on 06/01/06 12:31:40.

Change History

06/01/06 12:31:40 changed by ramiro

  • attachment date_hierarchy_i18n.diff added.

06/01/06 23:26:07 changed by adrian

  • status changed from new to closed.
  • resolution set to fixed.

(In [3056]) Fixed #2063 -- Made admin date_hierarchy i18n-friendly by using the new YEAR_MONTH_FORMAT and MONTH_DAY_FORMAT technical message IDs. Thanks, ramiro

08/04/07 19:37:58 changed by torokilopz

  • cc set to london.
  • keywords set to MESSAGE.

Hi thanks for really good website! Bye

08/04/07 20:52:33 changed by Simon G. <dev@simon.net.nz>

  • cc deleted.
  • keywords deleted.

Reverted twiddling. Go play elsewhere.

Add/Change #2063 ([patch] make date_hierarchy Admin feature fully i18n-able)




Change Properties
Action