#9366: date and time filters do not use localized strings, missing datetime
filter
-------------------------------------------+--------------------------------
Reporter: bthomas | Owner: nobody
Status: new | Milestone:
Component: Internationalization | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by Daniel Pope <[EMAIL PROTECTED]>):
@mtreddinick: This isn't really two items. This ticket is about the fact
that there's no way of using the existing datetime localisation
(http://code.djangoproject.com/browser/django/trunk/django/utils/translation/trans_real.py#L396)
in templates.
It makes sense to have the date and time filters do this if the i18n
machinery is enabled - otherwise these filters are just about useless in
internationalised applications. However, it's not sufficient to just have
date and time filters, as the preferred format for combined time and date
in different cultures ''may'' vary independently from date, time or any
combination of the two, so the solution also necessitates a datetime
filter. It's a two-part solution, not two different problems.
Anyway, FWIW, this is exactly what I need for the site I'm developing at
the moment.
--
Ticket URL: <http://code.djangoproject.com/ticket/9366#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
