Open issues

[Joost Cassee]

Hi all,

This mail is for everyone who is waiting for issues to be fixed. I know
there are many problems with DM currently. Although it basically works,
there are still many 'niche' problems (which may be big problems
depending on your web application). I have is good news and bad news to
report.

Good news: After Django 1.0 is release upgrading the Django i18n system
will be an important focus point. We are not the only people doing
multilingual models (see also django-transdb [1]) and there is already a
ticket collecting i18n ideas [2]. Marc Garcia (the ticket reporter) has
also written a blogpost about Django i18n issues [3].

Bad news: I can only speak for myself of course, but I do not expect DM
to do anything else but follow trunk to avoid breakage until Django 1.0.
No new features, admin sorting, etc. Sorry!

Regards,

Joost

[1] http://code.google.com/p/transdb/
[2] http://code.djangoproject.com/ticket/7980
[3] http://vaig.be/2008/07/26/django-i18n-status/

--
Joost Cassee
http://joost.cassee.net

[Joost Cassee]

My previous mail accidentally contained an tinymce application
attachment meant for another e-mail message. Nothing to do with my mail,
but if you want to know more: http://code.google.com/p/django-tinymce/

Joost

[Panos Laganakos]

I think we can wait, till Django 1.0 released, to get our stuff
together. I'm not even following DM trunk, 'cause I'm stuck at Django
0.96.*

My hope lies we'll have a much easier multilingual environment when we
get a change to work on 1.0+

--
Panos Laganakos

[Marcin Kaszynski]

Hi there,

On 21 Sie, 14:04, Joost Cassee <jo...@cassee.net> wrote:
> Good news: After Django 1.0 is release upgrading the Django i18n system
> will be an important focus point. We are not the only people doing
> multilingual models (see also django-transdb [1]) and there is already a
> ticket collecting i18n ideas [2]. Marc Garcia (the ticket reporter) has
> also written a blogpost about Django i18n issues [3].

right, although the focus seems to be on the i18n side (calendars,
formatting, interface texts), not multilingual content.

> Bad news: I can only speak for myself of course, but I do not expect DM
> to do anything else but follow trunk to avoid breakage until Django 1.0.
> No new features, admin sorting, etc. Sorry!

Yep, this is pretty much how it looks from my point of view as well.
DM already does everything I personally needed it for and it is clear
that recently I've had very little time to push it further as a
hobby. Were it not for help from Joost, Fabio and others DM would
very likely still be broken for Django trunk (thanks!).

So, I don't expect to have more time for DM in the nearest time,
definitely not enough to simultaneously develop new stuff and fix
problems with Django trunk on its road to 1.0 (although I think it
already passed all the planned backwards-incompatible changes).

Cheers,
-mk