Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (athena.apache.org: domain of
 Magnus.Haraldsen.Amundsen@computas.com designates 193.71.42.14 as permitted
 sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [C22] i18n
Date: Mon, 23 Jun 2008 11:26:21 +0200
Message-ID: <495295EE69BB4B4AAE73D1B0D8AD551803058029@ATLAS.computas.int>
Thread-Topic: [C22] i18n
Thread-Index: AcjVEZKwH8zczWMDTd+vskEgZTKhlgAAMYIg
References: <24686756.1214211959078.JavaMail.Administrator@XANADU>
 <24706281.1214212421218.JavaMail.Administrator@XANADU>
From: "Magnus Haraldsen Amundsen" <Magnus.Haraldsen.Amundsen@computas.com>
To: <users@cocoon.apache.org>

It's written to the JX Template using:

<c:messages>
  <jx:out value=3D"#{messages}" xmlize=3D"true"/>
</c:messages>

Where the jx:out contains a Java String that looks like this:

<c:messages>
  <c:message>
    <i18n:text key=3D"provided_ok"/>
  </c:message>
</c:messages>

When I look at the source after all the transforms, the String that came =
from Java looks like this:

<c:messages>
  <c:message>
    Provided URL validated.
  </c:message>
</c:messages>

So it's being translated, and it's not that it's treated as a regular =
string.=20

Other text that isn't i18n looks like this:

<c:messages>
  <c:message>
    En status m=E5 velges.
  </c:message>
</c:messages>

So I don't see why the i18n text shouldn't be displayed in the same way =
as the non-i18n text is.=20

- Magnus


-----Original Message-----
From: Askild Aaberg Hofs=F8y Olsen [mailto:askild@xangeli.com]=20
Sent: 23. juni 2008 11:13
To: users@cocoon.apache.org
Subject: Re: [C22] i18n

Magnus Haraldsen Amundsen wrote:
>
> The i18nTransformer works when I follow the 2.1 documentation, but=20
> we've found that <i18n:text> tags that we've hardcoded in the Java=20
> code doesn't get translated. It seems as it only translates=20
> <i18n:text> tags that we've added in the JX templates and the XSLT=20
> stylesheets.
>
My guess is that your <i18n:text> in Java is just treated as the the=20
string "<i18n:text>..</>", and are never parsed as an element in the =
stream.

If you look at the resulting XML before the i18n-transformer, do you see =

them as "&lt;18n:text&gt;"?

Askild


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

IMPORTANT NOTICE:
This message may contain confidential information. 
If you have received this e-mail in error, do not use, copy or 
distribute it. Do not open any attachments. Delete it immediately from
your system and notify the sender promptly by e-mail that you 
have done so. Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org