On 7/14/06, Carlos Yoder <[EMAIL PROTECTED]>
I'm a beliver that any tool should make the simple trivial and the difficult possible. To that end, I don't think there is a universal solution to pluralization. If a few small changes can get the existing solution to cover a few more languages (including Slovenian) with 'simple' pluralization strategies, then I think we should take the opportunity.
Then, if Ivan wants to contribute a 'declention' template tag that supports Russian pluralization (and is flexible enough to handle other languages with 'complex' pluralization, e.g., Latin), I'd be happy to add it. It would fit well in the django.templatetags.i18n package, especially if it took into account the current language page code when applying its strategy.
I believe the 'dictionary of all plurals' approach is what Rails does. From what I've seen, it's not a good approach. I don't know if this a problem with other languages, but with English, you end up with constant battles over the 'correct' plural (is it viruses or virii? octopuses, octopus or octopodes?) as a result of the multiple base-languages that have contributed to English over the years, persistent errors in usage, and disagreements over descriptive versus prescriptive generation of vocabulary. Then, to make things worse, the whole thing falls apart when you find a word that isn't in the plural dictionary. I, for one, would oppose the introduction of this approach.
Russ Magee %-)
What do you think, Russell?
I'm a beliver that any tool should make the simple trivial and the difficult possible. To that end, I don't think there is a universal solution to pluralization. If a few small changes can get the existing solution to cover a few more languages (including Slovenian) with 'simple' pluralization strategies, then I think we should take the opportunity.
Then, if Ivan wants to contribute a 'declention' template tag that supports Russian pluralization (and is flexible enough to handle other languages with 'complex' pluralization, e.g., Latin), I'd be happy to add it. It would fit well in the django.templatetags.i18n package, especially if it took into account the current language page code when applying its strategy.
I believe the 'dictionary of all plurals' approach is what Rails does. From what I've seen, it's not a good approach. I don't know if this a problem with other languages, but with English, you end up with constant battles over the 'correct' plural (is it viruses or virii? octopuses, octopus or octopodes?) as a result of the multiple base-languages that have contributed to English over the years, persistent errors in usage, and disagreements over descriptive versus prescriptive generation of vocabulary. Then, to make things worse, the whole thing falls apart when you find a word that isn't in the plural dictionary. I, for one, would oppose the introduction of this approach.
Russ Magee %-)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
