Corrected some inconsistent headings in docs/ref/templates/builtins.txt.

previous conditions fail. These clauses are optional.

Boolean operators

^^^^^^^^^^^^^^^^^

"""""""""""""""""

:ttag:`if` tags may use ``and``, ``or`` or ``not`` to test a number of

variables or to negate a given variable::

:ttag:`if` tags may also use the operators ``==``, ``!=``, ``<``, ``>``,

``<=``, ``>=`` and ``in`` which work as follows:

``==`` operator

^^^^^^^^^^^^^^^

~~~~~~~~~~~~~~~

Equality. Example::

    {% endif %}

``!=`` operator

^^^^^^^^^^^^^^^

~~~~~~~~~~~~~~~

Inequality. Example::

    {% endif %}

``<`` operator

^^^^^^^^^^^^^^

~~~~~~~~~~~~~~

Less than. Example::

    {% endif %}

``>`` operator

^^^^^^^^^^^^^^

~~~~~~~~~~~~~~

Greater than. Example::

    {% endif %}

``<=`` operator

^^^^^^^^^^^^^^^

~~~~~~~~~~~~~~~

Less than or equal to. Example::

    {% endif %}

``>=`` operator

^^^^^^^^^^^^^^^

~~~~~~~~~~~~~~~

Greater than or equal to. Example::

    {% endif %}

``in`` operator

^^^^^^^^^^^^^^^

~~~~~~~~~~~~~~~

Contained within. This operator is supported by many Python containers to test

whether the given value is in the container. The following are some examples

    {% endif %}

``not in`` operator

^^^^^^^^^^^^^^^^^^^

~~~~~~~~~~~~~~~~~~~

Not contained within. This is the negation of the ``in`` operator.

The comparison operators cannot be 'chained' like in Python or in mathematical

notation. For example, instead of using::

    {% if a > b and b > c %}

Filters

^^^^^^^

"""""""

You can also use filters in the :ttag:`if` expression. For example::

    {% endif %}

Complex expressions

^^^^^^^^^^^^^^^^^^^

"""""""""""""""""""

All of the above can be combined to form complex expressions. For such

expressions, it can be important to know how the operators are grouped when the

Sometimes that is better for clarity anyway, for the sake of those who do not

know the precedence rules.

.. templatetag:: ifchanged

ifchanged

        It is {% now "SHORT_DATETIME_FORMAT" %}

You can also use the syntax ``{% now "Y" as current_year %}`` to store the

output (as a string) inside a variable. This is useful if you want to use

``{% now %}`` inside a template tag like :ttag:`blocktrans` for example::

Regroups a list of alike objects by a common attribute.

This complex tag is best illustrated by way of an example: say that "places" is a list of cities represented by dictionaries containing ``"name"``, ``"population"``, and ``"country"`` keys:

This complex tag is best illustrated by way of an example: say that "places" is

a list of cities represented by dictionaries containing ``"name"``,

``"population"``, and ``"country"`` keys:

.. code-block:: python

        {'name': 'Tokyo', 'population': '33,000,000', 'country': 'Japan'},

    ]

...and you'd like to display a hierarchical list that is ordered by country, like this:

...and you'd like to display a hierarchical list that is ordered by country,

like this:

* India

  * Tokyo: 33,000,000

You can use the ``{% regroup %}`` tag to group the list of cities by country.

The following snippet of template code would accomplish this::

    {% regroup cities|dictsort:"country" by country as country_list %}

Grouping on other properties

^^^^^^^^^^^^^^^^^^^^^^^^^^^^

""""""""""""""""""""""""""""

Any valid template lookup is a legal grouping attribute for the regroup

tag, including methods, attributes, dictionary keys and list items. For

urlizetrunc

^^^^^^^^^^^

Converts URLs and email addresses into clickable links just like urlize_, but truncates URLs

longer than the given character limit.

Converts URLs and email addresses into clickable links just like urlize_, but

truncates URLs longer than the given character limit.

**Argument:** Number of characters that link text should be truncated to,

including the ellipsis that's added if truncation is necessary.