From 6183e0cb207e1c0dc3e3e563917a75b09077abef Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Sun, 3 Feb 2008 01:49:34 +0000 Subject: [PATCH] Clarified that filter arguments are passed as a single string to the translation support. Refs #6326. git-svn-id: http://code.djangoproject.com/svn/django/trunk@7059 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/i18n.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/i18n.txt b/docs/i18n.txt index 1ae3024157..78404d4503 100644 --- a/docs/i18n.txt +++ b/docs/i18n.txt @@ -292,6 +292,14 @@ translation string. Example:: In this case, both the tag and the filter will see the already-translated string, so they don't need to be aware of translations. +.. note:: + In this example, the translation infrastructure will be passed the string + ``"yes,no"``, not the individual strings ``"yes"`` and ``"no"``. The + translated string will need to contain the comma so that the filter + parsing code knows how to split up the arguments. For example, a German + translator might translate the string ``"yes,no"`` as ``"ja,nein"`` + (keeping the comma intact). + .. _Django templates: ../templates_python/ Working with lazy translation objects