Changes between Initial Version and Version 3 of Ticket #24913


Ignore:
Timestamp:
Jun 4, 2015, 6:02:27 AM (9 years ago)
Author:
Ana Balica
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #24913

    • Property Triage Stage Unreviewed → Accepted
    • Property Needs tests set
    • Property Owner changed from nobody to Ana Balica
    • Property Status new → assigned
    • Property Summary localize filter tag not work for thousand separator then USE_L10N is False → Localize filter tag doesn't work for thousand separator then USE_L10N is False

  • Ticket #24913 – Description

    initial v3  
    1 in settings.py
     1In settings.py set
    22'''USE_L10N = False
    33USE_THOUSAND_SEPARATOR = True'''
    44
    5 it template
     5In the template do this:
     6{{{
    67 {% localize on %}
    78      {{ object.price }}
    89 {% endlocalize %}
     10}}}
    911or
    10     {{ object.price|localize }}
     12{{{
     13{{ object.price|localize }}
     14}}}
    1115
    12 but there is no affect
     16Switching on the localization doesn't trigger the `USE_THOUSAND_SEPARATOR` setting in case it's set to True.
    1317
    1418I think in util.formats.number_format function should be something like this
     19{{{
    1520 if use_l10n:
    1621      force_grouping = True
     22}}}
    1723
    1824
    19 
Back to Top