test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Removed obsolete doc references to javascript_catalog.

This commit is contained in:
Samir Shah 2017-09-08 07:19:48 +03:00 committed by Tim Graham
parent 6e4c6281db
commit 4ac2ab30f5
3 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/releases/1.3.txt
View File

@ -583,8 +583,8 @@ domain):
translations shipped with applications by using the :setting:`LOCALE_PATHS`
setting is now possible for this domain too. These translations have higher
precedence than the translations of Python packages passed to the
:ref:`javascript_catalog view <javascript_catalog-view>`. Paths listed first
have higher precedence than the ones listed later.
``javascript_catalog()`` view. Paths listed first have higher precedence than
the ones listed later.
* Translations under the ``locale`` subdirectory of the *project directory*
have never been taken in account for JavaScript translations and remain in

2
docs/releases/1.7.txt
View File

@ -1742,7 +1742,7 @@ will be removed in Django 1.9. You can simply remove the
--------------------------------------
``javascript_quote()`` was an undocumented function present in ``django.utils.text``.
It was used internally in the :ref:`javascript_catalog view <javascript_catalog-view>`
It was used internally in the ``javascript_catalog()`` view
whose implementation was changed to make use of ``json.dumps()`` instead.
If you were relying on this function to provide safe output from untrusted
strings, you should use ``django.utils.html.escapejs`` or the

7
docs/topics/i18n/translation.txt
View File

@ -960,8 +960,6 @@ The main solution to these problems is the following ``JavaScriptCatalog`` view,
which generates a JavaScript code library with functions that mimic the
``gettext`` interface, plus an array of translation strings.
.. _javascript_catalog-view:
The ``JavaScriptCatalog`` view
------------------------------
@ -2071,9 +2069,8 @@ translations for the same literal:
.. seealso::
The translations for literals included in JavaScript assets are looked up
following a similar but not identical algorithm. See the
:ref:`javascript_catalog view documentation <javascript_catalog-view>` for
more details.
following a similar but not identical algorithm. See
:class:`.JavaScriptCatalog` for more details.
In all cases the name of the directory containing the translation is expected to
be named using :term:`locale name` notation. E.g. ``de``, ``pt_BR``, ``es_AR``,