> From: KOZLOV Roman [mailto:[EMAIL PROTECTED]]
> Konstantin, thank you for the reply.
>
> Problem: bug of i18n in Cocoon 2.0.1 related to
> "untranslated-text" because of
> keys divided by parser.
> Suggested workaround (not confirmed):
> It seems that using "concat" function for concatenation
Konstantin, thank you for the reply.
Problem: bug of i18n in Cocoon 2.0.1 related to "untranslated-text" because of
keys divided by parser.
Suggested workaround (not confirmed):
It seems that using "concat" function for concatenation of empty string and a
key in construction like helps to avoid
> From: Piroumian Konstantin [mailto:[EMAIL PROTECTED]]
> > From: KOZLOV Roman [mailto:[EMAIL PROTECTED]]
...
> > 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?
>
>
> 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
ca
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.
It seems that using "concat" function for concatenation of empty string
and a key in construction like
helps to avoid such a key dividing.
C
