Clarified i18n docs concerning verbose_name and verbose_name_plural - fixes #7102
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9009 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
cfcfc456e9
commit
b0da050b83
|
@ -184,10 +184,11 @@ If you don't like the verbose name ``ugettext_lazy``, you can just alias it as
|
|||
class MyThing(models.Model):
|
||||
name = models.CharField(help_text=_('This is the help text'))
|
||||
|
||||
Always use lazy translations in :ref:`Django models <topics-db-models>`. It's a
|
||||
good idea to add translations for the field names and table names, too. This
|
||||
means writing explicit ``verbose_name`` and ``verbose_name_plural`` options in
|
||||
the ``Meta`` class, though::
|
||||
Always use lazy translations in :ref:`Django models <topics-db-models>`.
|
||||
Field names and table names should be marked for translation or else they
|
||||
will not be translated in the admin interface. This means writing explicit
|
||||
``verbose_name`` and ``verbose_name_plural`` options in the ``Meta`` class,
|
||||
though::
|
||||
|
||||
from django.utils.translation import ugettext_lazy as _
|
||||
|
||||
|
|
Loading…
Reference in New Issue