new i18n feature

Hi guys Following up on a previsous discussion: http://groups.google.com/group/django-developers/browse_thread/thread/4c7b2ce86bcd990e/3731676c2134ea63 I've submitted a (rought) patch: http://code.djangoproject.com/ticket/7158 Fell free to comment, improve etc. - aD --~--~-~--~~---

bug report (flagged as spam on django trac) : simple data model yieds bug in admin page

This simple data model makes it impossible to display 'C' instance list in admin pages (loads forever : eats up all memory) : ** content of models.py ** from django.db import models class A(models.Model): b = models.ForeignKey("B") class B(models.Model): i_a = models.ForeignKey(A, rela

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

Hi, Trying to sum up the discussions so far I would say that Wolfram's syntax seems to be the preferred one : i.e. letting the logic go into the translated string but keeping the strings to translate in one bit. I wasn't that in favor of this solution at first but I confess I'm much more convin

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

Hi, First, I'd like to thank all people involved in this discussion for the quality of the insightful remarks and reactions they made on my first proposed syntax. I'm trying to imagine improvements to my proposed syntax based on the comments here ... unfortunately, I always find good reason

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

Hi, I agree that my proposed syntax was a little bit horrible ... but I really wonder if it can be different. Your syntax is interesting but : - I'm not sure it's really "djangoic" in the sense that it introduce a new way to declare markup '[[' and ']]' - the other problem I see is that it

i18n missing feature ... continued (proposed solution for the upcoming sprint)

Hi, Following up on a previous discussion about an important but complex i18n missing feature : http://groups.google.com/group/django-developers/browse_thread/thread/c88b582fa4764aaa I've been thinking over and over about the problem and came up with an idea of a proposed syntax that I want

Django translation missing feature / status ?

Hi, Back again on the django missing i18n feature in template (see thread : http://groups.google.com/group/django-developers/browse_thread/thread/c88b582fa4764aaa/665af6639a099ec8 ) Is there any impovements/thoughts on this ? Maybe I should post a trac entry just not to forget this (?) -- AD

Re: django translation feature missing (?)

Hi again, I would be happy to know you're impressions about the above explanation ... if I made my point clear or not, or if you have any objection why this would not be a useful feature ... Regards, -- AD --~--~-~--~~~---~--~~ You received this message beca

Re: django translation feature missing (?)

I'm not sure if this could be easily integrated into django's translation mecanism ... but I'm pretty convinced a feature is missing : The thing is that you want to render a sentence like "go to the page registration form" with a link on "registration form" ... but you dont want the translated se

Re: django translation feature missing (?)

Hi, Thanks a lot for the response. Actually, I "dare" to reply here because I think what follows might be a hint for the developers if they agree that the feature I'm talking about is worth a look. Such a translation feature is for instance available in Zope/Plone translation mecanism : h

django translation feature missing (?)

Hi, After taking a look at the django translation mecanism, I did not find a feature (I think) that is mandatory for what I'm trying to do : I'd like to have a translatable message that displays (in a page) something like : "This has been done by the user xxx" ... and of course, the "xxx" is