well, i dont like the translatable fields with different extensions either. but maybe someone else might (for his reasons, maybe a performance matter (although i don't know how much the difference would be really). the only thing I am advocating is to write everything uncoupled so that if someone _wants_ to write a backend that arranges things like this, he can, without having to alter the model and view code.
> Shouldn't the untranslated > field just return an empty value and then the template could suggest a > link to the original text reporting about the missing translation? how i would use it in my site is on the top i would have a text saying that the translation is not available, and then display the original below. (a direct "languange" link would "change" languange in the session, maybe changing the UI languange too) soo a shortcut to do this would be neat, but can also be done with two separate queries. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
