> I'm also nursing some wacky ideas for how to support translated URLsWhat I really dislike about localeurl is that it requires
> (I mean, translations of the actual URLs so the words in them
> correspond the active locale). I haven't been able to find any
> discussion on how people do this, so it's either a bad idea or a
> really hard problem or both. Still, if anybody's interested, drop me a
> line. I can share my crackpot schemes. :)
monkey-patching urlresolvers.reverse(). Malcolm Tredinnick dropped a
remark the other day on django-developers:
On 17 sep, 02:14, Malcolm Tredinnick <malc...@pointy-stick.com> wrote:
> You can already put any object you like that has a resolve() method intoSo here is my idea: localeurl could be based on some class pretending to
> urlpatterns(). That object can see every single pattern that passes
> through if it is matched for the pattern ''. We have to *some* kind of
> root object and it happens to be RegexURLResolver.
be a RegexPattern / RegexURLResolver combination. Not sure yet how that
would work, but this would fit in with other special URL mangling
This could work something like this:
Locale dependent paths would go into localepatterns. This would also
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.