id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
18932	Buildin template tags seem to break i18n	houmie	nobody	"Within my template as long as I have the following, the template automatically converts the datetime from UTC into my currently selected timezone. And I can also switch to a different culture (US to UK format) and the date and time format do change accordingly. 


{{{
{% load l10n %}
{% for item in calls %}
     <td>{{ item.conversation_datetime }}</td>
     <td>{{ item.conversation_datetime }}</td>
{% endfor %}
}}}


Now all I need to do is to extract the localized date for the former and localized time for the latter. So I thought lets bang a template tag in there and life is good.


{{{
{% load l10n %}
{% for item in calls %}
     <td>{{ item.conversation_datetime|date }}</td>
     <td>{{ item.conversation_datetime|time }}</td>
{% endfor %}
}}}


But if life was good, I wouldn't be sitting here and writing this would I? ;) The moment these filters are set, the format for these two fields seems to be fixed to the US culture. Date format is mm/dd/yyyy and time is 12 hrs am/pm.

Selecting the British language as I did before successfully has no longer any effect.

Please see a demo attached to this ticket."	New feature	closed	Internationalization		Normal	invalid	i18n		Unreviewed	0	0	0	0	1	0