[Zope3-dev] i18n:translate and message id

[Florent Guillaume]

On Mon, 2002-09-09 at 16:44, Barry A. Warsaw wrote:
> >>>>> "FG" == Florent Guillaume <fg@nuxeo.com> writes:
>     FG> For the record, I consider TALES the better choice seeing that
>     FG> otherwise there would be no way to have a computed message id
>     FG> for translation without explicitely calling some translation
>     FG> service.
> 
> Do you have a use case for needing a computed message id?


Actually I lied, we can do computed message ids, but that's not elegant.
The ones I have (they're from Plone) are all a variation of:

<span tal:omit-tag="" i18n:translate=""><span
      tal:replace="item/importance">Importance</span></span>

<span tal:omit-tag="" i18n:translate=""><span
      tal:replace="tab/name">Tab Name</span></span>


Note that the current Zope 2.7 (and Zope 3) code does not allow the
shorter form (which is allowed by Lalo's AltPTi18n):

<span tal:replace="tab/name" i18n:translate="">Tab Name</span>

Which is a quite acceptable way to do computed message ids.


Anyway I'm quite happy with the status quo now that I'm used to it.

Florent
-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 87  http://nuxeo.com  mailto:fg@nuxeo.com