Philipp von Weitershausen wrote:
Florent Guillaume wrote:
[snip]
I agree that the use case of having translations containing HTML is
important, and thus that we'll have to make sure do_insertStructure_tal
also does correct interpolation when faced with a MessageID.
The Zope 3's TALGenerator/T
Florent Guillaume wrote:
[snip]
I agree that the use case of having translations containing HTML is
important, and thus that we'll have to make sure do_insertStructure_tal
also does correct interpolation when faced with a MessageID.
I now have a monkey patch that patches in a two line modifica
Jim Fulton wrote:
> I still don't like the implicit translation of message ids,
I thought like that, too. You really would want implicit translation of
message ids, though, not because implicitness is the right choice here,
but because of general separation of concerns. This is along the same
line
Florent Guillaume wrote:
> Martijn Faassen wrote:
>
>> Zope 2.8 *is* actually interpolating and translating message ids
>> correctly *without* i18n:translate already. I think that this is the
>> same as Zope 3's (deprecated) behavior.
>>
>> The problem is when 'structure' is used in TALES. If this
Martijn Faassen wrote:
Zope 2.8 *is* actually interpolating and translating message ids
correctly *without* i18n:translate already. I think that this is the
same as Zope 3's (deprecated) behavior.
The problem is when 'structure' is used in TALES. If this isn't used,
translations happen normal
Martijn Faassen wrote:
Current (deprecated) behavior of Zope 3
If a message id is defined in python, such as _("Foo"), it gets
translated by the page template engine automatically when it enters
through a tal:content, tal:replace, or tal:attributes. No
Martijn Faassen wrote:
> My proposal is to recommend the use of i18n:translate for ZPT
> translation only, and let the ZPT engine automatically translate
> messages when they come from Python.
+1
Godefroid and now Martijn managed to convince me on this one :).
Basically, like Martijn, I've come
