test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.5.x] Updated documentation on localflavor translations 

to account for the deprecation of django.contrib.localflavor in 1.5.

Refs #19482.
This commit is contained in:
Aymeric Augustin 2012-12-26 14:33:47 +01:00
parent 0c79e5e347
commit e2396bf122
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/ref/contrib/localflavor.txt
View File

@ -142,13 +142,14 @@ 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 newly-created ``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`.
If you're still using the legacy ``localflavor`` application, you must include
:mod:`django.contrib.localflavor` in :setting:`INSTALLED_APPS` (that will
raise a ``DeprecationWarning``).