Fixed #31006 -- Doc'd backslash escaping in date/time template filters.

This commit is contained in:
Ryan Cheley 2019-11-22 18:38:27 -08:00 committed by Mariusz Felisiak
parent 3b347a8a00
commit a1f14ee3e5
1 changed files with 12 additions and 1 deletions

View File

@ -1451,7 +1451,9 @@ used. Assuming the same settings as the previous example::
{{ value|date }} {{ value|date }}
outputs ``9 de Enero de 2008`` (the ``DATE_FORMAT`` format specifier for the outputs ``9 de Enero de 2008`` (the ``DATE_FORMAT`` format specifier for the
``es`` locale is ``r'j \d\e F \d\e Y'``. ``es`` locale is ``r'j \d\e F \d\e Y'``). Both "d" and "e" are
backslash-escaped, because otherwise each is a format string that displays the
day and the timezone name, respectively.
You can combine ``date`` with the :tfilter:`time` filter to render a full You can combine ``date`` with the :tfilter:`time` filter to render a full
representation of a ``datetime`` value. E.g.:: representation of a ``datetime`` value. E.g.::
@ -2177,6 +2179,15 @@ For example::
If ``value`` is equivalent to ``datetime.datetime.now()``, the output will be If ``value`` is equivalent to ``datetime.datetime.now()``, the output will be
the string ``"01:23"``. the string ``"01:23"``.
Note that you can backslash-escape a format string if you want to use the
"raw" value. In this example, both "h" and "m" are backslash-escaped, because
otherwise each is a format string that displays the hour and the month,
respectively::
{% value|time:"H\h i\m" %}
This would display as "01h 23m".
Another example: Another example:
Assuming that :setting:`USE_L10N` is ``True`` and :setting:`LANGUAGE_CODE` is, Assuming that :setting:`USE_L10N` is ``True`` and :setting:`LANGUAGE_CODE` is,