From a20aae414e762e4d9043e76b0bf8eccd334c8ebc Mon Sep 17 00:00:00 2001 From: Patryk Zawadzki Date: Mon, 19 Feb 2018 19:09:33 +0100 Subject: Fixed #29144 -- Made untranslated strings for territorial language variants use translations from the generic language variant. --- docs/topics/i18n/translation.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'docs/topics') diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt index 31ee71a05e..c205c15d4c 100644 --- a/docs/topics/i18n/translation.txt +++ b/docs/topics/i18n/translation.txt @@ -2082,7 +2082,13 @@ translations for the same literal: In all cases the name of the directory containing the translation is expected to be named using :term:`locale name` notation. E.g. ``de``, ``pt_BR``, ``es_AR``, -etc. +etc. Untranslated strings for territorial language variants use the translations +of the generic language. For example, untranslated ``pt_BR`` strings use ``pt`` +translations. + +.. versionchanged:: 2.1 + + Fallback to the generic language as described above was added. This way, you can write applications that include their own translations, and you can override base translations in your project. Or, you can just build -- cgit v1.3