Author: adrian
Date: 2007-05-12 12:11:19 -0500 (Sat, 12 May 2007)
New Revision: 5213
Modified:
django/trunk/docs/newforms.txt
Log:
Fixed some ReST errors in docs/newforms.txt from [5212]
Modified: django/trunk/docs/newforms.txt
===================================================================
--- django/trunk/docs/newforms.txt 2007-05-12 17:02:44 UTC (rev 5212)
+++ django/trunk/docs/newforms.txt 2007-05-12 17:11:19 UTC (rev 5213)
@@ -942,7 +942,8 @@
``TimeField`` ``TimeField``
``URLField`` ``URLField`` with ``verify_exists`` set
to the model field's ``verify_exists``
- ``USStateField`` ``CharField with ``widget=USStateSelect``
+ ``USStateField`` ``CharField`` with
+ ``widget=USStateSelect``
(``USStateSelect`` is from
``django.contrib.localflavor.us``)
``XMLField`` ``CharField`` with ``widget=Textarea``
@@ -1094,7 +1095,7 @@
sensible defaults; if you have a ``DateField`` in your model, chances are you'd
want that to be represented as a ``DateField`` in your form. But
``form_for_model()`` gives you the flexibility of changing the form field type
-for a given model field. You do this by specifying a *formfield callback*.
+for a given model field. You do this by specifying a **formfield callback**.
A formfield callback is a function that, when provided with a model field,
returns a form field instance. When constructing a form, ``form_for_model()``
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
