From e2ec7b47b3acb0338d971942ca7ffd36c2a4d8f4 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Wed, 26 Dec 2012 14:33:47 +0100 Subject: [PATCH] Updated documentation on localflavor translations to account for the removal of django.contrib.localflavor in 1.6. Refs #19482. --- docs/ref/contrib/localflavor.txt | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/docs/ref/contrib/localflavor.txt b/docs/ref/contrib/localflavor.txt index 84569feebe6..7c2e56451d3 100644 --- a/docs/ref/contrib/localflavor.txt +++ b/docs/ref/contrib/localflavor.txt @@ -142,13 +142,10 @@ default formats. Here's an example of how to use them:: class MyForm(forms.Form): my_date_field = generic.forms.DateField() -Internationalization of localflavor -=================================== +Internationalization of localflavors +==================================== -Localflavor has its own catalog of translations, in the directory -``django/contrib/localflavor/locale``, and it's not loaded automatically like -Django's general catalog in ``django/conf/locale``. If you want localflavor's -texts to be translated, like form fields error messages, you must include -:mod:`django.contrib.localflavor` in the :setting:`INSTALLED_APPS` setting, so -the internationalization system can find the catalog, as explained in -:ref:`how-django-discovers-translations`. +To activate translations for a ``localflavor`` application, you must include +the application's name (e.g. ``django_localflavor_jp``) in the +:setting:`INSTALLED_APPS` setting, so the internationalization system can find +the catalog, as explained in :ref:`how-django-discovers-translations`.