> From: KOZLOV Roman [mailto:[EMAIL PROTECTED]]
>
> Hello,
>
> It's just concerning i18n transformer in Cocoon 2.0.1.
> There is known bug of i18n related to "untranslated-text" because of
> keys divided by parser.
I'd say "there was a known bug". I've fixed that bug several months ago. You
can just get a newer version from CVS (2.0.3 branch contains fixed version).
> It seems that using "concat" function for concatenation of
> empty string
> and a key in construction like
> <i18n:text><xsl:value-of select="concat('',LABEL)"/></i18n:text>
> helps to avoid such a key dividing.
It's interesting how it can solve this problem? According to SAX
specification, the parser can break character data into chunks on its
discretion. So, you cannot guarantee that some other parser or in some other
condition this will work too.
>
> Could someone, who is more familiar with these issues confirm
> that this
> workaround could help to avoid the bug or it just decrease probability
> of keys dividing?
Just get the newer version. There were some other changes since 2.0, but you
can use the CVS revision history to get the needed version. (I'd point you
to the needed version, but have problems accessing CVS currently).
Konstantin
>
> Thank you in advance,
> Roman
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
