Django’s formatting system is capable of displaying dates, times and numbers in\ntemplates using the format specified for the current\nlocale. It also handles localized input in forms.
\nTwo users accessing the same content may see dates, times and numbers formatted\nin different ways, depending on the formats for their current locale.
\n\n\nWhen formatting is enabled, Django can use localized formats when parsing\ndates, times and numbers in forms. That means it tries different formats for\ndifferent locales when guessing the format used by the user when inputting data\non forms.
\n\nTo enable a form field to localize input and output data use its localize\nargument:
class CashRegisterForm(forms.Form):\n product = forms.CharField()\n revenue = forms.DecimalField(max_digits=4, decimal_places=2, localize=True)\nFor country specific form fields, validation, and data formats that are not\nincluded in Django itself, consider using the django-localflavor\npackage, which provides localized form fields and utilities for many countries\nand regions (documentation).
\nDjango tries to use a locale specific format whenever it outputs a value in a\ntemplate.
\nHowever, it may not always be appropriate to use localized values –\nfor example, if you’re outputting JavaScript or XML that is designed\nto be machine-readable, you will always want unlocalized values. You\nmay also want to use localization in selected templates, rather than\nusing localization everywhere.
\nTo allow for fine control over the use of localization, Django\nprovides the l10n template library that contains the following\ntags and filters.
localizeLink to this heading#Forces localization of a single value.
\nFor example:
\n{% load l10n %}\n\n{{ value|localize }}\nTo disable localization on a single value, use unlocalize. To\ncontrol localization over a large section of a template, use the\nlocalize template tag.
unlocalizeLink to this heading#Forces a single value to be printed without localization.
\nFor example:
\n{% load l10n %}\n\n{{ value|unlocalize }}\nTo force localization of a single value, use localize. To\ncontrol localization over a large section of a template, use the\nlocalize template tag.
Returns a string representation for numbers (int, float, or\nDecimal) with the localization settings formats\napplied.
Django provides format definitions for many locales, but sometimes you might\nwant to create your own, because a format file doesn’t exist for your locale,\nor because you want to overwrite some of the values.
\nTo use custom formats, specify the path where you’ll place format files\nfirst. To do that, set your FORMAT_MODULE_PATH setting to the\npackage where format files will exist, for instance:
FORMAT_MODULE_PATH = [\n "mysite.formats",\n "some_app.formats",\n]\nFiles are not placed directly in this directory, but in a directory named as\nthe locale, and must be named formats.py. Be careful not to put sensitive\ninformation in these files as values inside can be exposed if you pass the\nstring to django.utils.formats.get_format() (used by the date\ntemplate filter).
To customize the English formats, a structure like this would be needed:
\nmysite/\n formats/\n __init__.py\n en/\n __init__.py\n formats.py\nwhere formats.py contains custom format definitions. For example:
THOUSAND_SEPARATOR = "\\xa0"\nto use a non-breaking space (Unicode 00A0) as a thousand separator,\ninstead of the default for English, a comma.
Some locales use context-sensitive formats for numbers, which Django’s\nlocalization system cannot handle automatically.
\nThe Swiss number formatting traditionally varies depending on context. For\nexample, monetary values may use a dot as decimal separator (Fr. 23.50),\nwhile measurements often use a comma (22,5 m). Django’s localization system\ndoes not support such context-specific variations automatically.
The locale format provided by Django uses the generic separators, a comma for\ndecimal and a space for thousand separators.
\n