Browse files

Clarified i18n docs concerning verbose_name and verbose_name_plural - f…

…ixes #7102

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent cfcfc45 commit b0da050b830ac902f16cc5f6891ea64ed9ae1457 Simon Willison committed Sep 11, 2008
Showing with 5 additions and 4 deletions.
  1. +5 −4 docs/topics/i18n.txt
@@ -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,
from django.utils.translation import ugettext_lazy as _

0 comments on commit b0da050

Please sign in to comment.