On Mon, 2008-03-31 at 05:12 -0300, Marinho Brandao wrote: > Malcolm and Alex, > > thanks, but I gave up. This was not a good idea :)
I realise what you're trying to do, but personally, if you want a URL per locale, I'd shove a locale identifier into the URL, rather than trying to translate the word. That way you only have to capture one portion of the URL and pass it to your view and that will tell you the locale. Yes, it's not as readable for everybody in all languages, but it does help you establish a hierarchy of resources with the locale-dependent portions being at the leaves of the tree. Regards, Malcolm -- Success always occurs in private and failure in full view. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
