From 8e970f4835074d887c7f65b53c9dbb067f953e64 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Sat, 15 Sep 2007 14:46:41 +0000 Subject: [PATCH] Fixed #5492 -- Removed some bad markup. Thanks, msaelices. git-svn-id: http://code.djangoproject.com/svn/django/trunk@6286 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/i18n.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/i18n.txt b/docs/i18n.txt index 0a078c24d2..4794b39d5b 100644 --- a/docs/i18n.txt +++ b/docs/i18n.txt @@ -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`` 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. +specify in either the info_dict or the URL. You hook it up like this:: @@ -817,8 +817,8 @@ pluralizations). Creating JavaScript translation catalogs ---------------------------------------- -You create and update the translation catalogs the same way as the other Django -translation catalogs -- with the {{{make-messages.py}}} tool. The only +You create and update the translation catalogs the same way as the other +Django translation catalogs -- with the make-messages.py tool. The only difference is you need to provide a ``-d djangojs`` parameter, like this:: make-messages.py -d djangojs -l de