#13450: Can django's i18n internationalization middleware offer language
selection
by URL?
-------------------------------------------+--------------------------------
Reporter: benoitcsirois | Owner: nobody
Status: closed | Milestone:
Component: Internationalization | Version: 1.1
Resolution: wontfix | Keywords: i18n
internationalization seo languages urls
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm fairly certain what you describe can be achieved by setting
request.urlconf in the middleware.
As for adding this to Django; my inclination is that this probably isn't
suitable for core. It strikes me as a design pattern that requires a lot
more infrastructure than just a middleware - it would also require
language-sensitive models etc, which is the domain of external projects
like django-rosetta.
However, this isn't a particularly strongly held position; if you want to
make your case for the inclusion of a feature like this, feel free to
advocate for it on django-developers (preferably after the 1.2 release is
out the door, so we can give it the proper attention).
--
Ticket URL: <http://code.djangoproject.com/ticket/13450#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
