#2063 closed enhancement (fixed)
[patch] make date_hierarchy Admin feature fully i18n-able
| Reported by: | Ramiro Morales | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | contrib.admin | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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 (1)
Change History (4)
by , 19 years ago
| Attachment: | date_hierarchy_i18n.diff added |
|---|
comment:1 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 17 years ago
| Cc: | added |
|---|---|
| Keywords: | MESSAGE added |
Hi
thanks for really good website!
Bye
comment:3 by , 17 years ago
| Cc: | removed |
|---|---|
| Keywords: | MESSAGE removed |
Reverted twiddling. Go play elsewhere.
Note:
See TracTickets
for help on using tickets.
(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