diff options
| author | Elif T. Kus <elifkus@gmail.com> | 2016-01-03 12:56:22 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-01-22 12:12:17 -0500 |
| commit | bca9faae95db2a92e540fbd08505c134639916fe (patch) | |
| tree | 92b34dd8ecf8cf5432c25d43292ebc83b7919350 /docs/releases/1.2.txt | |
| parent | 79d0a4fdb0d13ba6a843dace2b90ab44e856bd85 (diff) | |
Fixed #26020 -- Normalized header stylings in docs.
Diffstat (limited to 'docs/releases/1.2.txt')
| -rw-r--r-- | docs/releases/1.2.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt index 065764c3a3..d680c1e72b 100644 --- a/docs/releases/1.2.txt +++ b/docs/releases/1.2.txt @@ -309,7 +309,7 @@ Django's :doc:`internationalization framework </topics/i18n/index>` has been exp with locale-aware formatting and form processing. That means, if enabled, dates and numbers on templates will be displayed using the format specified for the current locale. Django will also use localized formats when parsing data in -forms. See :ref:`Format localization <format-localization>` for more details. +forms. See :doc:`/topics/i18n/formatting` for more details. ``readonly_fields`` in ``ModelAdmin`` ------------------------------------- @@ -1072,10 +1072,10 @@ to provide localizers the possibility to translate date and time formats. They were translatable :term:`translation strings <translation string>` that could be recognized because they were all upper case (for example :setting:`DATETIME_FORMAT`, :setting:`DATE_FORMAT`, :setting:`TIME_FORMAT`). -They have been deprecated in favor of the new :ref:`Format localization -<format-localization>` infrastructure that allows localizers to specify that -information in a ``formats.py`` file in the corresponding -``django/conf/locale/<locale name>/`` directory. +They have been deprecated in favor of the new :doc:`/topics/i18n/formatting` +infrastructure that allows localizers to specify that information in a +``formats.py`` file in the corresponding ``django/conf/locale/<locale name>/`` +directory. GeoDjango --------- @@ -1089,7 +1089,7 @@ following sections provide information on the most-popular APIs that were affected by these changes. ``SpatialBackend`` -^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~ Prior to the creation of the separate spatial backends, the ``django.contrib.gis.db.backend.SpatialBackend`` object was @@ -1117,7 +1117,7 @@ Would need to be changed:: PostGISAdaptor = connection.ops.Adapter ``SpatialRefSys`` and ``GeometryColumns`` models -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In previous versions of GeoDjango, :mod:`django.contrib.gis.db.models` had ``SpatialRefSys`` and ``GeometryColumns`` models for querying |