Fixed #18625 -- Removed old-style use of url tag

To specify the URL you want to redirect to after the comment has been posted,

you can include a hidden form input called ``next`` in your comment form. For example::

    <input type="hidden" name="next" value="{% url my_comment_was_posted %}" />

    <input type="hidden" name="next" value="{% url 'my_comment_was_posted' %}" />

.. _notes-on-the-comment-form:

.. code-block:: html+django

    {% url arch-summary 1945 %}

    {% url full-archive 2007 %}

    {% url 'arch-summary' 1945 %}

    {% url 'full-archive' 2007 %}

Even though both URL patterns refer to the ``archive`` view here, using the

``name`` parameter to ``url()`` allows you to tell them apart in templates.

Reverse URL lookups cannot be carried out within the ``blocktrans`` and should

be retrieved (and stored) beforehand::

    {% url path.to.view arg arg2 as the_url %}

    {% url 'path.to.view' arg arg2 as the_url %}

    {% blocktrans %}

    This is a URL: {{ the_url }}

    {% endblocktrans %}

.. code-block:: html+django

    <script type="text/javascript" src="{% url django.views.i18n.javascript_catalog %}"></script>

    <script type="text/javascript" src="{% url 'django.views.i18n.javascript_catalog' %}"></script>

This uses reverse URL lookup to find the URL of the JavaScript catalog view.

When the catalog is loaded, your JavaScript code can use the standard

    {% trans "View this category in:" %}

    {% for lang_code, lang_name in languages %}

        {% language lang_code %}

        <a href="{% url category slug=category.slug %}">{{ lang_name }}</a>

        <a href="{% url 'category' slug=category.slug %}">{{ lang_name }}</a>

        {% endlanguage %}

    {% endfor %}