I like this quite a bit. It's clean, and it allows for a common i18n pattern
where the footer contains a translation link for each supported language, and
the language names are localized to themselves (i.e. "Español | Français |
Deutsch").
Sam
On 2011-07-04, at 5:23 AM, brocaar wrote:
> On Monday, July 4, 2011 10:04:10 AM UTC+2, Jannis Leidel wrote:
> Agreed, what about just "language", e.g.:
>
> {% language lang_code %}
> {% trans "Register account" %}: {% url account:register %}
> {% endlanguage %}
>
>
>
> I agree too that the tag name in my example is quite ugly, it was only to
> clarify my idea ;) Just "language" sounds perfect!
>
> Orne
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/huy6SEXMIBkJ.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
