django.contrib.humanize filters are not well localized

[Dmitry Pisklov]

In some countries (namely, Russia), "decimal point" is actually comma, and thousands separator is space (as comma used as decimal part separator!). This needs to be fixed in humanize filters, as they are useless in ru locale right now.

[Bas Peschier]

Duplicate of #16562 which actually discovered the problem.

[Dmitry Pisklov]

Not a duplicate of #16562 - it's completely different bug referring to USE_THOUSANDS_SEPARATOR, and is has nothing to do with localization of separator character.

[Jannis Leidel]

I'm not sure what this ticket is reporting, to be honest, except that something "is not well localized". Feel free to re-open if you have a clear explanation of what you expected you find, but got instead. Any detail would be much appreciated.

[anonymous]

Well, here's an example:
I have the following code in template:

{obj.price|intcomma}

If the object price is 2500, the output is:

2,500

disregarding of locale which is RU in my case.

The problem is, in number of countries (​http://en.wikipedia.org/wiki/Decimal_mark#Countries_using_Arabic_numerals_with_decimal_comma) comma is decimal separator. So the output above is read as 2.500 ( two and five hundred thousandths ).
Instead, the decimal separator should be chosen according to locale, and in my case it should be just space char, so that my number will look like:
2 500
and any decimal number would look like:
1 234.56

Hope that makes things clear.

[anonymous]

oooops.
Just looked in SVN - looks like it was fixed at r16168.
I'm using older version.
Thanks jezdez for fixing - sorry for disturbing:)

[Jacob]

Milestone 1.4 deleted