Edited some recent docs changes

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9042 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2008-09-16 05:31:00 +00:00
parent 3b0bf9805d
commit 772639c692
2 changed files with 8 additions and 8 deletions

View File

@ -96,7 +96,7 @@ e-mail address::
>>> f = ContactForm(data)
>>> f.is_valid()
False
.. attribute:: Form.errors
Access the :attr:`~Form.errors` attribute to get a dictionary of error
@ -530,7 +530,7 @@ string or Unicode object, respectively::
>>> unicode(f['subject'])
u'<input id="id_subject" type="text" name="subject" maxlength="100" />'
Form objects define a custom ``__iter__`` method which allows you to loop
Form objects define a custom ``__iter__()`` method, which allows you to loop
through their fields::
>>> f = ContactForm()

View File

@ -295,9 +295,9 @@ templates:
Reusable form templates
-----------------------
If your site uses the same rendering logic for forms in multiple places you
can create a template that contains just the form loop and use the
:ttag:`include` tag to reuse it in your other templates::
If your site uses the same rendering logic for forms in multiple places, you
can reduce duplication by saving the form's loop in a standalone template and
using the :ttag:`include` tag to reuse it in other templates::
<form action="/contact/" method="POST">
{% include "form_snippet.html" %}
@ -314,7 +314,7 @@ can create a template that contains just the form loop and use the
{% endfor %}
If the form object passed to a template has a different name within the
context you can alias it using the :ttag:`with` tag::
context, you can alias it using the :ttag:`with` tag::
<form action="/comments/add/" method="POST">
{% with comment_form as form %}
@ -323,8 +323,8 @@ context you can alias it using the :ttag:`with` tag::
<p><input type="submit" value="Submit comment" /></p>
</form>
You can also create a custom :ref:`inclusion
tag<howto-custom-template-tags-inclusion-tags>`.
If you find yourself doing this often, you might consider creating a custom
:ref:`inclusion tag<howto-custom-template-tags-inclusion-tags>`.
Further topics
==============