#5997: Pluralization support too limited
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Component: Internationalization
Version: SVN | Resolution: wontfix
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------+-------------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
If you search the ticket archive, you will see that this issue has come up
before (See #794, #2202). It has also been proposed and discussed at
length on the mailing lists. The outcome of those discussions has
historically been to reject this idea.
Pluralization is almost impossible to handle in such a way as to be both
comprehensive enough to support languages like Polish with complex
pluralization requirements, while remaining simple to use for those
languages that have relatively simple pluralization requirements (Cases
1-5 in the page you reference).
If you have a specific suggestion for an elegant way to handle Polish (and
other complex pluralization cases) that is compatible with existing usage,
feel free to reopen this ticket.
--
Ticket URL: <http://code.djangoproject.com/ticket/5997#comment:2>
Django Code <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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
