just use the localize/unlocalize format separator
https://docs.djangoproject.com/en/1.9/topics/i18n/formatting/#std:templatefilter-localize
For example:
{% load l10n %}
{{ value|localize }}
To disable localization on a single value, use unlocalize. To control
localization over a large section of a template, use the localize
template tag. unlocalize¶
Forces a single value to be printed without localization.
For example:
{% load l10n %}
{{ value|unlocalize }}
To force localization of a single value, use localize. To control
localization over a large section of a template, use the localize
template tag.
edit:
see
https://docs.djangoproject.com/en/1.9/topics/i18n/translation/#switching-language-in-templates
{% load i18n %}
{% get_current_language as LANGUAGE_CODE %}
<!-- Current language: {{ LANGUAGE_CODE }} -->
<p>{% trans "Welcome to our page" %}</p>
{% language 'en' %}
{% get_current_language as LANGUAGE_CODE %}
<!-- Current language: {{ LANGUAGE_CODE }} -->
<p>{% trans "Welcome to our page" %}</p>
{% endlanguage %}
you can switch languages to force the display if localize/unlocalize does not work
floatformat
is not a custom filter, why not use it? – Hagaifloatformat
returns a localized float using commas instead of points (or dots) – Cordi