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

Fixed #5492 -- Removed some bad markup. Thanks, msaelices. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6286 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-09-15 14:46:41 +00:00
parent 9d18227a56
commit 8e970f4835
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/i18n.txt
View File

@ -752,7 +752,7 @@ The main solution to these problems is the ``javascript_catalog`` view, which
sends out a JavaScript code library with functions that mimic the ``gettext`` sends out a JavaScript code library with functions that mimic the ``gettext``
interface, plus an array of translation strings. Those translation strings are interface, plus an array of translation strings. Those translation strings are
taken from the application, project or Django core, according to what you taken from the application, project or Django core, according to what you
specify in either the {{{info_dict}}} or the URL. specify in either the info_dict or the URL.
You hook it up like this:: You hook it up like this::
@ -817,8 +817,8 @@ pluralizations).
Creating JavaScript translation catalogs Creating JavaScript translation catalogs
---------------------------------------- ----------------------------------------
You create and update the translation catalogs the same way as the other Django You create and update the translation catalogs the same way as the other
translation catalogs -- with the {{{make-messages.py}}} tool. The only Django translation catalogs -- with the make-messages.py tool. The only
difference is you need to provide a ``-d djangojs`` parameter, like this:: difference is you need to provide a ``-d djangojs`` parameter, like this::
make-messages.py -d djangojs -l de make-messages.py -d djangojs -l de