From 556eb6770146f26a7f01f786034d8b3ec879ed05 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Fri, 20 Mar 2015 19:59:10 +0100 Subject: [PATCH] Fixed #23520 -- Explained that custom plural forms should be avoided Thanks aruseni for the report. --- docs/topics/i18n/translation.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt index 268ebf5fca..0f7e76756b 100644 --- a/docs/topics/i18n/translation.txt +++ b/docs/topics/i18n/translation.txt @@ -263,6 +263,15 @@ In a case like this, consider something like the following:: a format specification for argument 'name', as in 'msgstr[0]', doesn't exist in 'msgid' +.. note:: Plural form and po files + + Django does not support custom plural equations in po files. As all + translation catalogs are merged, only the plural form for the main Django po + file (in ``django/conf/locale//LC_MESSAGES/django.po``) is + considered. Plural forms in all other po files are ignored. Therefore, you + should not use different plural equations in your project or application po + files. + .. _contextual-markers: Contextual markers