Opened 8 years ago

Closed 8 years ago

#7102 closed (fixed)

change in i18n documentation to emphasise that unless verbose_name and verbose_name_plural are marked for translation, they will not be translated.

Reported by: kenneth gonsalves <lawgon@…> Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: i18n
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The current sentence regarding verbose_name is:

"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:"

This could be changed like this:

"Field names and table names must be marked for translation otherwise 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:"

Attachments (1)

7102.diff (885 bytes) - added by Chris Beaven 8 years ago.

Download all attachments as: .zip

Change History (3)

Changed 8 years ago by Chris Beaven

Attachment: 7102.diff added

comment:1 Changed 8 years ago by Chris Beaven

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedDesign decision needed

comment:2 Changed 8 years ago by simon

Resolution: fixed
Status: newclosed

(In [9009]) Clarified i18n docs concerning verbose_name and verbose_name_plural - fixes #7102

Note: See TracTickets for help on using tickets.
Back to Top