#14844: i18n blocktrans tag pluralization feature limited by gettext constraints
and unique local tag context
-------------------------------------------+--------------------------------
Reporter: ramiro | Owner: nobody
Status: new | Milestone: 1.3
Component: Internationalization | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Comment (by lukeplant):
I think the solution proposed by Claude sounds about right. The problem is
that it causes a regression - for the case of English,
`verbose_name_plural` will be ignored. AFAICS, [13998] never fixed the bug
it was supposed to fix - can someone confirm that? If so, my apologies,
and I will go ahead and revert it in order to get the i18n workflow fixed.
Then we need to agree on a plan for `verbose_name_plural`. The annoying
thing is that if you remove it, you have to enable the i18n framework just
to get plurals in the admin for English. A significant amount of time and
effort had gone in to make the i18n framework optional, and I don't think
we should break that, since there will be many deployments that use only
English. One option is to use `verbose_name_plural` only if i18n is
disabled, and document this clearly.
--
Ticket URL: <http://code.djangoproject.com/ticket/14844#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
