> - regarding the problem that the translation is maintained in
> chucks : if not then there is the presence of logic in the translation
> string, which is not possible I think. If you agree on that, it means
> that the translation _has_ to be maintained in chucks
This nails the main problem imho.
That is simply the decision that has to be taken.
And for the sake of semantics and allowing _better_ translations, by
not tearing up strings that logically belong together I think this
logic in the template is what you have to sacrify.
May be some post processing or a tool can ensure the correctness of
the translation.
> - regarding the fact that the syntax is too complex, I think this is
> due to the new tag : {% insideblocktrans %} in my syntax. The problem
> is that, even if my example uses a link, one could think of many other
> ways to use it : for instance to simply 'highlight' part of a
> dynamically translated string (with <strong> for instance) so I see a
> necessity to let the user have full control of what is inside the
> logic that will be sort of 'injected' into the translated parts.
> That's why I can't manage to see any way to use the {% with %} tag as
> suggested ...
>
> -alain
>
>
> >
>
--
cu
Wolfram
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
