Ticket #13417: 13417-r13135.diff

docs/topics/i18n/internationalization.txt

@@ -449 +449 @@
 The ``javascript_catalog`` view
 -------------------------------
 
-The main solution to these problems is the ``javascript_catalog`` view, which
-sends out a JavaScript code library with functions that mimic the ``gettext``
-interface, plus an array of translation strings. Those translation strings are
-taken from the application, project or Django core, according to what you
-specify in either the info_dict or the URL.
+.. module:: django.views.i18n
+
+.. function:: def javascript_catalog(request, domain='djangojs', packages=None)
+
+The main solution to these problems is the ``django.views.i18n.javascript_catalog``
+view, which sends out a JavaScript code library with functions that mimic the
+``gettext`` interface, plus an array of translation strings. Those translation
+strings are taken from the application, project or Django core, according to what
+you specify in either the info_dict or the URL.
 
 You hook it up like this::
 
@@ -471 +475 @@
 those catalogs are merged into one catalog. This is useful if you have
 JavaScript that uses strings from different applications.
 
+By default, the view uses the ``djangojs`` gettext domain which can be
+changed by the ``domain`` argument.
+
 You can make the view dynamic by putting the packages into the URL pattern::
 
     urlpatterns = patterns('',
@@ -541 +548 @@
 The ``set_language`` redirect view
 ==================================
 
+.. function:: def set_language(request)
+
 As a convenience, Django comes with a view, ``django.views.i18n.set_language``,
 that sets a user's language preference and redirects back to the previous page.