Yes, that would work AND would keep me from having presentation details
in the view implementation. Cool.
Thanks for the link! I hadn't found that yet.
Daniel
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djang
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
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 jus
On 20-Aug-06, at 1:22 PM, [EMAIL PROTECTED] wrote:
> I tried this, but neither
> {% include {% trans "welcome.html" %} %}
> nor
> {% include "{% blocktrans %}welcome.html{% endblocktrans %}" %}
> appear to work (make-messages doesn't even seem to find these
> translation strings).
>
> What would
Hi.
I'm just in the process of translating my project and have hit a
stumbling block.
I use several includes for longer text which I don't want to have
cluttering up my template.
Can I translate the parameter to an {% include %} template tag?
I have a file welcome.html, which includes a lot of
5 matches
Mail list logo
