Opened 18 years ago

Closed 18 years ago

Last modified 6 years ago

#3373 closed Uncategorized (wontfix)

verbose_name_plural and internationalization

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

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.

Change History (4)

comment:1 by Simon G. <dev@…>, 18 years ago

Keywords: i18n added
Triage Stage: UnreviewedDesign decision needed

comment:2 by Malcolm Tredinnick, 18 years ago

Resolution: wontfix
Status: newclosed

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).

comment:3 by Dylan Young, 6 years ago

Easy pickings: unset
Severity: Normal
Type: Uncategorized
UI/UX: unset

I would reopen this. The reasons for closing are kind of absurd (consider a similar statement: we don't use annotations in our contrib packages, so we should ex the QuerySet.annotate method: huh?).

Aside form that, it simplifies application code: verbose_name and verbose_name_plural are collapsed into just verbose_name.

Version 1, edited 6 years ago by Dylan Young (previous) (next) (diff)

comment:4 by Tim Graham, 6 years ago

Dylan, feel free to write to the DevelopersMailingList with your proposal.

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