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

Updated documentation on localflavor translations 

to account for the removal of django.contrib.localflavor in 1.6.

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

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

@ -142,13 +142,10 @@ default formats. Here's an example of how to use them::
class MyForm(forms.Form): class MyForm(forms.Form):
my_date_field = generic.forms.DateField() my_date_field = generic.forms.DateField()
Internationalization of localflavor Internationalization of localflavors
=================================== ====================================
Localflavor has its own catalog of translations, in the directory To activate translations for a ``localflavor`` application, you must include
``django/contrib/localflavor/locale``, and it's not loaded automatically like the application's name (e.g. ``django_localflavor_jp``) in the
Django's general catalog in ``django/conf/locale``. If you want localflavor's :setting:`INSTALLED_APPS` setting, so the internationalization system can find
texts to be translated, like form fields error messages, you must include the catalog, as explained in :ref:`how-django-discovers-translations`.
: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`.