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
This commit is contained in:
parent
f45dab3061
commit
6183e0cb20
|
@ -292,6 +292,14 @@ translation string. Example::
|
||||||
In this case, both the tag and the filter will see the already-translated
|
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.
|
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/
|
.. _Django templates: ../templates_python/
|
||||||
|
|
||||||
Working with lazy translation objects
|
Working with lazy translation objects
|
||||||
|
|
Loading…
Reference in New Issue