﻿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
33281	intcomma template filter doesn't depend on the USE_L10N setting.	Demetris Stavrou	nobody	"Given the following configuration:

{{{
# settings.py
LANGUAGE_CODE = 'el-gr'
USE_L10N = False
USE_THOUSAND_SEPARATOR = True
THOUSAND_SEPARATOR = "",""
NUMBER_GROUPING = 3
}}}

{{{
# views.py
class ThousandView(TemplateView):
    template_name = ""thousand_template.html""

    def get_context_data(self, **kwargs):
        context = super().get_context_data(**kwargs)
        context[""test_number""] = 1234
        return context
}}}

{{{
# thousand_template.html
{% load humanize %}
<!DOCTYPE html>
<html lang=""en"">
<head>
  <meta charset=""UTF-8"">
  <meta http-equiv=""X-UA-Compatible"" content=""IE=edge"">
  <meta name=""viewport"" content=""width=device-width, initial-scale=1.0"">
  <title>Document</title>
</head>
<body>
  {{ test_number|intcomma }}
</body>
</html>
}}}

one would expect that the `test_number` value is rendered as `1,234`. However, it is rendered as `1.234`. I intentionally used `el-gr` because the locale defines the thousand separator to be `.`. As shown in the settings, this shouldn't matter since we use `USE_L10N=False`. However, it seems that it affects the result, because if `en-us` is used instead, then the number is rendered as `1,234`.

**Testing this with Django version 3.1.13, works as expected**, i.e. given the above configuration, the number is correctly rendered as `1,234`.

"	Uncategorized	closed	Template system	3.2	Normal	invalid		Claude Paroz	Unreviewed	0	0	0	0	0	0
