On 24.06.2011, at 23:52, Florian Apolloner wrote: > I would like to get some feedback on > https://code.djangoproject.com/ticket/16332 > Jacob suggested that the standard url-tag should take a lang argument > so we don't need an extra tag (okay, his actual concern was the > dislike of the name i18n_url ;)). I would like that idea too, but I am > somewhat worried about the implications; eg it would break as soon as > someone already has "lang" as param in his urlconf and using a > parameter like __lang isn't that nice either… > > Any thoughts on this?
As I said initially when we discussed this on IRC, I believe a "i18n_url" is good enough and would fit well with the other i18n related template tags. Besides the ambiguity of a potential keyword argument "lang", I'd like to mention that we specifically chose to use "i18n_patterns" as the name for the function that returns i18n-enabled URL patterns to be explicit about when a URL should be translated. I believe this pattern should also be applied to the template tag which a user might use to point to one of those translatable URLs. Jannis -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
