Code

Opened 7 years ago

Closed 7 years ago

#3373 closed (wontfix)

verbose_name_plural and internationalization

Reported by: Vitek Owned by: hugo
Component: Internationalization Version: master
Severity: Keywords: pluralization i18n
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In Czech (Polish, Russian etc..) are more than 2 forms. In English: 1 object, 2+ objects. We have: 1 objekt; 2-4 objekty; 0, 5+ objektů.
So if I define verbose_name and verbose_name_plural, translation in Admin interface under list of objects and other places, where i wont use it, is not correct.
Maybe there is a way to use ngettext (optional, for i18n sites) for verbose_name_plural, but i didn't found this.

Attachments (0)

Change History (2)

comment:1 Changed 7 years ago by Simon G. <dev@…>

  • Keywords i18n added
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

comment:2 Changed 7 years ago by mtredinnick

  • Resolution set to wontfix
  • Status changed from new to closed

We never put a numeric quantifier in front of the verbose_name_plural string when it is used in Django. So the multiple plural forms are not required.

Translators should just use whichever plural form they would normally used for a generic number of items (i.e. use the form you would use for "cars" in the sentence "All cars go through here" -- notice that we use the plural of car without a number).

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.