On Sat, Jun 25, 2011 at 6:58 AM, Jannis Leidel <lei...@gmail.com> wrote:
>
> 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.
>
On Sat, Jun 25, 2011 at 2:50 AM, maxk <klymys...@gmail.com> wrote:
> What do you think about something like below
>
> {% url viewname k1=v1, k2=v2 with lang=lang %}
Briefly discussed this via IRC th Jannis. I'm +1 on keeping the new tag
in the i18 ttag lib for the reasons exposed by Jannis. So a prefix like
'i18n_' would fit well IMHO. +1 on this.
Adding that functionality to the i18n tag can also work, I think.
Especially now that Jannis makes me see it wouldn't cause loading of the
i18n machinery for people with USE_i18N=False. But I'd like to
completely avoid the possibility of clashing with existing 'lang'
arguments and I'm not 100% convinced by the "with lang='xx'" part of the
proposed syntax. It is a hybrid between our 'old' "with var as alias"
and the new (from future) "var=alias" form. I'm -0 on this option
--
Ramiro Morales
--
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.
