#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 |
-------------------------------------------+--------------------------------
Changes (by ramiro):
* summary: i18b blocktrans tag pluralization feature limited by gettext
constraints and context => i18n blocktrans tag
pluralization feature limited by gettext
constraints and unique local tag context
Comment:
On IRC Jannis pointed to the work being done for #7817, #9456:
https://github.com/SmileyChris/django/compare/master...7817-include-with.
The syntax changes for ''blocktrans'' to be implemented mean we need to
find another syntax if the proposal is accepted as a solution for this
ticket.
I'd be inclined to implement the solution proposed by Claude for both
1.2.X and trunk now so to unbreak the i18n workflow (PO -> MO conversion
is broken ATM) and target a longer term solution for trunk once the
template syntax overhaul dust settles.
That longer term solution might involve to end the full reliance on
`verbose_name_plural` when pluralizing model names in Python code and
templates, for the benefit of locales with more than two plural forms. I
suspect the challenge would be to achieve that without interfering with or
complication English speaking Django core developers normal workflow so to
don't get the proposal rejected.
--
Ticket URL: <http://code.djangoproject.com/ticket/14844#comment:2>
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.
