Hi Gunter,
no, the namespace should not be an issue in this case. It would have
been if you had a wd:something attribute.
Maybe woody is parsing the wd:item before the i18n transformer does, and
woody removes the i18n:attr and/or transforms the wd:item to something
else. Try to see what arrives to the i18n:transformer by placing a view
on it, or by commenting out the rest of the pipeline fom the
i18n:transformer to the serializer and serializing out in xml, so that
you can see what is the input of the i18n transformer. You could also
try to pass the pipe thru the i18n:transformer before woody, but can't
remember if this is possible with woody at all.
Simone
Gunter D'Hondt wrote:
I'm trying to add an i18n text inside the attribute of a woody tag; it
works fine for the label tag using the standard i18n:text but it doesn't
work when using i18n:attr. Is this becourse the tag (wd:item) is inside a
namespace (wd)?
Regards,
Gunter D'Hondt
form definition snippet:
<wd:form
xmlns:wd="http://apache.org/cocoon/woody/definition/1.0";
xmlns:i18n="http://apache.org/cocoon/i18n/2.1";>
...
<wd:selection-list>
<wd:item i18n:attr="value" value="myi18nkey">
<wd:label>
<i18n:text>myi18nkey</i18n:text>
</wd:label>
</wd:item>
</wd:selection-list>
...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
