Loading docs/topics/i18n.txt +5 −4 Original line number Diff line number Diff line Loading @@ -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 Loading
docs/topics/i18n.txt +5 −4 Original line number Diff line number Diff line Loading @@ -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