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
25928	Documentation on THOUSAND_SEPARATOR and NUMBER_GROUPING is still misleading	Felix Dreissig	Wingston SHaron	"The `THOUSAND_SEPARATOR` and `NUMBER_GROUPING` settings are only used if the current locale doesn't specify a thousands separator. This has been reported in #15918 and the following sentence has been added to the documentation:

> Note that if USE_L10N is set to True, then the locale-dictated format has higher precedence and will be applied instead.

However, the same page of the documentation says about `USE_THOUSAND_SEPARATOR`:

> When USE_L10N is set to True and if this is also set to True, Django will use the values of THOUSAND_SEPARATOR and NUMBER_GROUPING to format numbers.

These two quotes are kind of contradictory, because obviously one really can't use `USE_THOUSAND_SEPARATOR` without `USE_L10N`. The latter quote is plain wrong in most cases, as most locales define thousands separators.

`THOUSAND_SEPARATOR` and `NUMBER_GROUPING` are really only respected if `USE_L10N = True`, `USE_THOUSAND_SEPARATOR = True` and the locale doesn't specify a thousands separator. I think it would be great to just use `USE_THOUSAND_SEPARATOR` without `USE_L10N` and manually set `THOUSAND_SEPARATOR` and `NUMBER_GROUPING`, but that is currently not possible.

Anyway, I think the discrepancy should at least be removed form the documentation.

Regards,
Felix"	Bug	closed	Documentation	dev	Normal	fixed		f30@…	Accepted	0	0	0	0	0	0