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
14181	Template tag needed to disable/force L10N formatting on a per-variable basis	Russell Keith-Magee	Benjamin Wohlwend	"The L10N support added in Django 1.2 is great, but there are times when you don't want to use L10N, regardless of any system settings.

#14164 is one manifestation of this problem. Outside of sitemaps, any data being rendered to XML (or any other format for data interchange) is generally going to need data to be rendered in ""english"" locale format.

A simple workaround is to render the value to a string in the context, so that the template renders a string, not an integer/float. However, a more general appoach is required.

Some possible options: A template filter to disable localization:
{{{
   {{ value|unlocalized }} 
}}}
A template filter to force a specific localization:
{{{
   {{ value|locale:""en"" }}
}}}
Or, template tag variants of the same:
{{{
   {% unlocalized %}
      {{ value }}
   {% endunlocalized %}

   {% localize ""en"" %}
      {{ value }}
   {% endlocalize %}
}}}

The ""localize"" filter is the easiest to implement, but probably not the easiest to use.

"		closed	Internationalization	1.2		fixed			Accepted	1	0	0	0	0	0