Opened 17 years ago
Closed 16 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: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | i18n | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
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)
Change History (3)
by , 17 years ago
comment:1 by , 17 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [9009]) Clarified i18n docs concerning verbose_name and verbose_name_plural - fixes #7102