[Zope3-dev] RFC: undeprecate auto-message id translation

Martijn Faassen faassen at infrae.com
Tue Dec 6 12:14:02 EST 2005


Hi there,

An amendment on the behavior in Zope 2.8 + Five 1.2; it's different than 
I thought and actually this is quite a relief to me (though there are 
still problems).

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 normally. If it is used, translations suddenly 
break, as do_insertStructure_tal is used instead of do_insertText_tal.

I can see that this makes sense if you "structure in" large pieces of 
HTML -- they won't have translations. It does however break a usecase 
where your message ids contain HTML. This isn't really clean, but very 
handy for translators sometimes, especially if they want to use HTML 
entities and the like. You can then use i18n:translate="" explicitly on 
the structure, which will cause the *string* to be translated, without 
interpolation happening. This put me on the wrong track initially, not 
realizing the impact of 'structure' on the functioning of the TAL 
interpreter.

Regards,

Martijn


More information about the Zope3-dev mailing list