Ticket #17240: internal-references.diff

File internal-references.diff, 4.1 KB (added by rabio, 4 years ago)
  • docs/intro/tutorial01.txt

    diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt
    index 8474d9e..8dc05c0 100644
    a b Save these changes and start a new Python interactive shell by running 
    704704For more information on model relations, see :doc:`Accessing related objects
    705705</ref/models/relations>`. For more on how to use double underscores to perform
    706 field lookups via the API, see `Field lookups`__. For full details on the
     706field lookups via the API, see :ref:`Field lookups <field-lookups-intro>`. For full details on the
    707707database API, see our :doc:`Database API reference </topics/db/queries>`.
    709 __ http://docs.djangoproject.com/en/1.2/topics/db/queries/#field-lookups
    711709When you're comfortable with the API, read :doc:`part 2 of this tutorial
    712710</intro/tutorial02>` to get Django's automatic admin working.
  • docs/releases/1.0.1.txt

    diff --git a/docs/releases/1.0.1.txt b/docs/releases/1.0.1.txt
    index 780dc53..37142a2 100644
    a b Welcome to Django 1.0.1! 
    77This is the first "bugfix" release in the Django 1.0 series, improving
    88the stability and performance of the Django 1.0 codebase. As such,
    9 Django 1.0.1 contains no new features (and, pursuant to `our
    10 compatibility policy`_, maintains backwards compatibility with Django
     9Django 1.0.1 contains no new features (and, pursuant to :doc:`our
     10compatibility policy </misc/api-stability/>`, maintains backwards
     11compatibility with Django
    11121.0), but does contain a number of fixes and other
    1213improvements. Django 1.0.1 is a recommended upgrade for any
    1314development or deployment currently using or targeting Django 1.0.
    4748* A fix to the application of autoescaping for literal strings passed
    4849  to the ``join`` template filter. Previously, literal strings passed
    49   to ``join`` were automatically escaped, contrary to `the documented
    50   behavior for autoescaping and literal strings`_. Literal strings
     50  to ``join`` were automatically escaped, contrary to :ref:`the
     51  documented behavior for autoescaping and literal strings
     52  <string-literals-and-automatic-escaping>`. Literal strings
    5153  passed to ``join`` are no longer automatically escaped, meaning you
    5254  must now manually escape them; this is an incompatibility if you
    5355  were relying on this bug, but not if you were relying on escaping
    6062  documentation, including both corrections to existing documents and
    6163  expanded and new documentation.
    63 .. _our compatibility policy: http://docs.djangoproject.com/en/dev/misc/api-stability/
    6465.. _the Subversion log of the 1.0.X branch: http://code.djangoproject.com/log/django/branches/releases/1.0.X
    65 .. _the documented behavior for autoescaping and literal strings: http://docs.djangoproject.com/en/dev/topics/templates/#string-literals-and-automatic-escaping
  • docs/topics/db/models.txt

    diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
    index f907c23..65b2d59 100644
    a b whatever you want. For example:: 
    324324    should work; all are optional.
    326326    For details on accessing backwards-related objects, see the
    327     `Following relationships backward example`_.
     327    :ref:`Following relationships backward example <backwards-related-objects>`.
    329329    For sample code, see the `Many-to-one relationship model tests`_.
    331     .. _Following relationships backward example: http://docs.djangoproject.com/en/dev/topics/db/queries/#backwards-related-objects
    332331    .. _Many-to-one relationship model tests: http://code.djangoproject.com/browser/django/trunk/tests/modeltests/many_to_one
    334333Many-to-many relationships
  • docs/topics/templates.txt

    diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
    index 719fc67..17e5d69 100644
    a b to any variable that needs escaping. When auto-escaping is on, there's no 
    556556danger of the :tfilter:`escape` filter *double-escaping* data -- the
    557557:tfilter:`escape` filter does not affect auto-escaped variables.
     559.. _string-literals-and-automatic-escaping:
    559561String literals and automatic escaping
Back to Top