On 11/7/06, Bill de hOra <[EMAIL PROTECTED]> wrote: > Hey, > > I know Django has solid i18n support for templates/strings and content > negotiation in the request. But I was wondering how people are going > about managing translations of content or having a multilingual website > - eg supporting features like "read this in newspeak", or "browse this > site in klingon". More realistic examples would be Wikipedia or Plone's > ability to set the portal language. > > There's no direct support for this kind of thing in the core (that's > afaik, I haven't been following the trunk in the last couple of months). > And, if there's no standard patterns or models for this, is this worth > thinking about at as an extension app? In my part of the world, being > able to run a multilingual site is often a 'checkbox' requirement. > > cheers > Bill
I'd been reserching and trying to come up with some ideas on this matter, hoping to get to an elegant and simple solution since I'm involved with two django projects which will need content translation. Some months ago a similar thread was discused on this list: http://groups.google.com.uy/group/django-users/browse_thread/thread/ef78a6787a98bc68/2aabccc699388fad I think there are some interesting ideas there... so I took Georg ideas as a starting point, what do you think about his aproach? I'm definitely interested on working with others to see this feature in django in the future. gonz. -- Gonzalo Saavedra <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
