Ticket #16621: doc_typos.diff
File doc_typos.diff, 11.2 KB (added by , 13 years ago) |
---|
-
AUTHORS
172 172 eriks@win.tue.nl 173 173 Tomáš Ehrlich <tomas.ehrlich@gmail.com> 174 174 Dirk Eschler <dirk.eschler@gmx.net> 175 Bernhard Essl <me@bernhardessl.com> 175 176 Dan Fairs <dan@fezconsulting.com> 176 177 Marc Fargas <telenieko@telenieko.com> 177 178 Szilveszter Farkas <szilveszter.farkas@gmail.com> -
docs/topics/forms/modelforms.txt
713 713 Just like with ``ModelForms``, by default the ``clean()`` method of a 714 714 ``model_formset`` will validate that none of the items in the formset violate 715 715 the unique constraints on your model (either ``unique``, ``unique_together`` or 716 ``unique_for_date|month|year``). If you want to over ide the ``clean()`` method716 ``unique_for_date|month|year``). If you want to override the ``clean()`` method 717 717 on a ``model_formset`` and maintain this validation, you must call the parent 718 718 class's ``clean`` method:: 719 719 -
docs/releases/1.2-alpha-1.txt
23 23 --------------- 24 24 25 25 There have been large changes to the way that CSRF protection works, detailed in 26 :doc:`the CSRF documentat on </ref/contrib/csrf>`. The following are the major26 :doc:`the CSRF documentation </ref/contrib/csrf>`. The following are the major 27 27 changes that developers must be aware of: 28 28 29 29 * ``CsrfResponseMiddleware`` and ``CsrfMiddleware`` have been deprecated, and -
docs/releases/1.2.txt
426 426 --------------- 427 427 428 428 We've made large changes to the way CSRF protection works, detailed in 429 :doc:`the CSRF documentat on </ref/contrib/csrf>`. Here are the major changes you429 :doc:`the CSRF documentation </ref/contrib/csrf>`. Here are the major changes you 430 430 should be aware of: 431 431 432 432 * ``CsrfResponseMiddleware`` and ``CsrfMiddleware`` have been deprecated and -
docs/ref/forms/fields.txt
938 938 939 939 .. attribute:: ModelChoiceField.empty_label 940 940 941 By default the ``<select>`` widget used by ``ModelChoiceField`` will have a 942 anempty choice at the top of the list. You can change the text of this941 By default the ``<select>`` widget used by ``ModelChoiceField`` will have an 942 empty choice at the top of the list. You can change the text of this 943 943 label (which is ``"---------"`` by default) with the ``empty_label`` 944 944 attribute, or you can disable the empty label entirely by setting 945 945 ``empty_label`` to ``None``:: -
docs/ref/contrib/localflavor.txt
1363 1363 1364 1364 .. class:: uy.forms.UYDepartamentSelect 1365 1365 1366 A ``Select`` widget that uses a list of Uruguayan depart aments as its1366 A ``Select`` widget that uses a list of Uruguayan departments as its 1367 1367 choices. -
docs/ref/contrib/gis/install.txt
112 112 113 113 .. note:: 114 114 115 On Linux platforms, it may be necessar ry to run the ``ldconfig``115 On Linux platforms, it may be necessary to run the ``ldconfig`` 116 116 command after installing each library. For example:: 117 117 118 118 $ sudo make install … … 1202 1202 reg ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v GDAL_DATA /t REG_EXPAND_SZ /f /d "%GDAL_DATA%" 1203 1203 reg ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v PROJ_LIB /t REG_EXPAND_SZ /f /d "%PROJ_LIB%" 1204 1204 1205 For your convenience, these commands are available in the execu atble batch1205 For your convenience, these commands are available in the executable batch 1206 1206 script, :download:`geodjango_setup.bat`. 1207 1207 1208 1208 .. note:: -
docs/ref/contrib/gis/gdal.txt
937 937 4326 938 938 >>> print srs['TOWGS84', 4] # the fourth value in this wkt 939 939 0 940 >>> print srs['UNIT|AUTHORITY'] # For the units authority, have to use the pipe symbol e.940 >>> print srs['UNIT|AUTHORITY'] # For the units authority, have to use the pipe symbol. 941 941 EPSG 942 >>> print srs['UNIT|AUTHORITY', 1] # The authority value for the un tis942 >>> print srs['UNIT|AUTHORITY', 1] # The authority value for the units 943 943 9122 944 944 945 945 .. method:: attr_value(target, index=0) -
docs/ref/contrib/gis/deployment.txt
6 6 7 7 GeoDjango uses the GDAL geospatial library which is 8 8 not thread safe at this time. Thus, it is *highly* recommended 9 to not use threading when deploying -- in other words, use a 10 a n appropriate configuration of Apache or the prefork method9 to not use threading when deploying -- in other words, use an 10 appropriate configuration of Apache or the prefork method 11 11 when using FastCGI through another Web server. 12 12 13 13 Apache -
docs/ref/contrib/gis/geoquerysets.txt
301 301 Oracle 302 302 ~~~~~~ 303 303 304 Here the relation pattern is compr eised at least one of the nine relation304 Here the relation pattern is comprised at least one of the nine relation 305 305 strings: ``TOUCH``, ``OVERLAPBDYDISJOINT``, ``OVERLAPBDYINTERSECT``, 306 306 ``EQUAL``, ``INSIDE``, ``COVEREDBY``, ``CONTAINS``, ``COVERS``, ``ON``, and 307 307 ``ANYINTERACT``. Multiple strings may be combined with the logical Boolean -
docs/ref/contrib/flatpages.txt
85 85 subsequently raise a 404. 86 86 87 87 .. versionchanged:: 1.4 88 Redirects by the middl ware are permanent (301 status code) instead of88 Redirects by the middleware are permanent (301 status code) instead of 89 89 temporary (302) to match behavior of the 90 90 :class:`~django.middleware.common.CommonMiddleware`. 91 91 -
docs/ref/contrib/formtools/form-wizard.txt
100 100 in the :doc:`sessions documentation </topics/http/sessions>` on 101 101 how to enable sessions. 102 102 103 We will use the :class:`SessionWizardView` in all examples but is is complet ly103 We will use the :class:`SessionWizardView` in all examples but is is completely 104 104 fine to use the :class:`CookieWizardView` instead. As with your 105 105 :class:`~django.forms.Form` classes, this :class:`WizardView` class can live 106 106 anywhere in your codebase, but convention is to put it in :file:`views.py`. … … 263 263 .. method:: WizardView.get_form_initial(step) 264 264 265 265 Returns a dictionary which will be passed to the form for ``step`` as 266 ``initial``. If no initial data was provi ed while initializing the267 form wizard, a empty dictionary should be returned.266 ``initial``. If no initial data was provided while initializing the 267 form wizard, an empty dictionary should be returned. 268 268 269 269 The default implementation:: 270 270 … … 283 283 284 284 .. method:: WizardView.get_form_instance(step) 285 285 286 Returns a object which will be passed to the form for ``step`` as287 ``instance``. If no instance object was provi ed while initializing286 Returns an object which will be passed to the form for ``step`` as 287 ``instance``. If no instance object was provided while initializing 288 288 the form wizard, None be returned. 289 289 290 290 The default implementation:: … … 475 475 476 476 Please remember to take care of removing old files as the 477 477 :class:`WizardView` won't remove any files, whether the wizard gets 478 finished corre tly or not.478 finished correctly or not. 479 479 480 480 Conditionally view/skip specific steps 481 481 ====================================== -
docs/ref/contrib/admin/index.txt
967 967 .. versionadded:: 1.4 968 968 969 969 The ``get_ordering`` method takes a``request`` as parameter and 970 is expected to return a ``list`` or ``tuple`` for ordering simil iar970 is expected to return a ``list`` or ``tuple`` for ordering similar 971 971 to the :attr:`ordering` attribute. For example:: 972 972 973 973 class PersonAdmin(ModelAdmin): -
docs/ref/contrib/csrf.txt
417 417 Default: ``None`` 418 418 419 419 The domain to be used when setting the CSRF cookie. This can be useful for 420 easily allowing cross-subdomain requests to be ex luded from the normal cross420 easily allowing cross-subdomain requests to be excluded from the normal cross 421 421 site request forgery protection. It should be set to a string such as 422 422 ``".lawrence.com"`` to allow a POST request from a form on one subdomain to be 423 423 accepted by accepted by a view served from another subdomain. -
docs/ref/settings.txt
305 305 Default: ``None`` 306 306 307 307 The domain to be used when setting the CSRF cookie. This can be useful for 308 easily allowing cross-subdomain requests to be ex luded from the normal cross308 easily allowing cross-subdomain requests to be excluded from the normal cross 309 309 site request forgery protection. It should be set to a string such as 310 310 ``".lawrence.com"`` to allow a POST request from a form on one subdomain to be 311 311 accepted by accepted by a view served from another subdomain. … … 1997 1997 1998 1998 Default: ``False`` 1999 1999 2000 A boolean that specifies whet er to display numbers using a thousand separator.2000 A boolean that specifies whether to display numbers using a thousand separator. 2001 2001 If this is set to ``True``, Django will use values from 2002 2002 :setting:`THOUSAND_SEPARATOR` and :setting:`NUMBER_GROUPING` from current 2003 2003 locale, to format the number. :setting:`USE_L10N` must be set to ``True``,