Okay, I noticed this thread literally seconds after creating my own describing a very similar approach. I searched the group for 'multilingual', should also have checked 'translations'. The new thread should appear shortly.
My library also uses the internal Translation class, but I moved the definitions of translatable fields into Translation. I thought about adding multiple backends too (another useful backend is to have the translated field values in different columns in the model, so that you can get all translations as a single row from a SELECT statement, otherwise using translations for ordering gets tricky). I planned to use different names instead of Translation to specify which backend to use, but I do like the backend field. Anyway, it's good to see I'm not the only one interested in working on a generic solution :) -mk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
