On 30-09-2005, at 20:36, hugo wrote:
I did subclass the GNUTranslations, but actually if you want a db store, it's easy to integrate later on. For now I think staying withgettext and .po/.mo is the way to go - you can easily deliver .mo files with your django app to people that want to use your app, but you can'tas easily deliver database content.
I agree, I can continue to develop my database driven version as add- on application which will be compatible with your i18n implementation, so users can use .po/.mo based storage for the core and database based for own applications.
About plural forms, I can use something like this in the code:
t = translation('foo', 'bar')
msg = t.ngettext(x, 'singular', 'plural')
but, your implementation for template tag don't have any plural
support. You can probably add something like {% i18n ngettext(x,
'singular', 'plural') %}, patch is attached (untested).
But all that doesn't say that there shouldn't be any patches later onthat make the i18n stuff friendlier or better or easier - my patch justis there to make i18n _possible_ :-)
And that's is great, I'm just started to think that no one but me is interested in i18n part of the django :).
tag.diff
Description: Binary data
--- Nebojša Đorđević - nesh Studio Quattro - Niš - SCG http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/ Registered Linux User 282159 [http://counter.li.org]
