Hi Piotr,
Unlikely. The current development focus is to get a v1.0 out the door;
primarily this means completing the newforms changeover (including
newforms-admin), finishing the queryset refactor, and a handful of
other small bugs and features.
If we extend this list to include every feature that each user thinks
is essential, we will never get v1.0 out the door. For me (and many
people I know), aggregate columns are a must-have feature;
multi-lingual features are less important. Everyone has different
priorities, and we can't satisfy everyone at once.
I should also point out that being in the core doesn't grant code
special magic powers. I haven't looked at django-multilingual myself,
but if it works now, it won't work any better by virtue of being part
of the Django core. If anything, being an external project is a
benefit, as those developers with a particular interest in
multilingual features don't need to have access to the Django core
repository in order to contribute directly to the multilingual
project.
Yours,
Russ Magee %-)
Same here. I'm currently working on a German/English-site and also
just have for each field that's supposed to be multilingual actually 2
fields and an additional property for convenience:
class Document(models.Model):
title_de = models.CharField(...)
title_en = models.CharField(...)
...
title = property(_get_title_for_current_language)
- Horst