On 8/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Um, yes. I realize that would work. I guess I was looking for a more
> "automagical" solution (which would not force me to change the template
> when I come up with a French or Kisuaheli version of trogger :-) ).
>
> I think I'll go with passing the name of the file to include in the
> Context and then just translate that in my view using _("welcome.html")
> -- that would keep working when ading additional languages. This
> approach just has the drawback of putting stuff that belongs in the
> display template (which HTML files to include in order to render the
> page) into the view implementation, where i feel it doesn't really
> belong.
>
> Daniel
>
>
See expr http://code.djangoproject.com/wiki/ExprTag-- I like python! My Blog: http://www.donews.net/limodou My Django Site: http://www.djangocn.org NewEdit Maillist: http://groups.google.com/group/NewEdit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
