From b0da050b830ac902f16cc5f6891ea64ed9ae1457 Mon Sep 17 00:00:00 2001 From: Simon Willison Date: Thu, 11 Sep 2008 02:32:59 +0000 Subject: [PATCH] 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 --- docs/topics/i18n.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/topics/i18n.txt b/docs/topics/i18n.txt index 8ba2f9c89f..00cfd18ff7 100644 --- a/docs/topics/i18n.txt +++ b/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 `. 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 `. +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 _