[Zope3-dev] Re: Use case not covered for translation of message ids

Jim Fulton jim at zope.com
Tue Sep 28 09:55:30 EDT 2004


Martijn Faassen wrote:
> Jim Fulton wrote:
> 
>> Martijn Faassen wrote:
> 
> 
>>>
>>> Doesn't that require setting the message id in it? But the message id 
>>> is already available, in the i18n string. What does the 
>>> i18n:translate attribute look like in this case?
>>
>>
>>
>> If the source string and the message id are the same, then
>> the value of the i18n:translate attribute is empty.  In that case,
>> the attribute functions to indicate that translation should be done.
> 
> 
> What if the i18n:translate attribute is not empty and we have a i18n 
> string coming from the application? Is this an error?

Good question. I'm inclined to say think that
in the case of a node that has *both* a translate attribute and a
tal:contents or tal:replace attribute, it should be an error to
specify the message id in the translate attribute, as it makes no
sense to use a static message id for dynamic data.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org


More information about the Zope3-dev mailing list