No, I gave that a shot, but the CDATA element is maintained intact through
all processing steps showing "The <b>first</b> paragraph" as text also in
HTML.
Thanks anyway for the tip :)
Thanks also Konstantin for your answer! It saved me alot of trial and error.
Regards,
Gustav
-----Original Message-----
From: Michael McKibben [mailto:[EMAIL PROTECTED]]
Sent: den 25 september 2001 19:52
To: [EMAIL PROTECTED]
Subject: Re: i18n & <translation> with subelements
Would it work if the text was wrapped as CDATA? I.e.
<translation xml:lang="en"><![CDATA[The <b>first</b>
paragraph]]></translation>
Regards,
--mike
On Tue, 25 Sep 2001, Piroumian, Konstantin wrote:
> > I am developing an international website with mainly static content, but
> > have run into a problem related to i18n.
> >
> > I would like to translate whole paragraphs of text using the i18n
> framework,
> > but would like these paragraphs to contain some more or less html-like
> tags.
> > The problem is that I18nTransformer seems to only copy the last text
node
> > from a <translation> tag.
>
> Yes, that's true. i18ntransformer does not support nested XML. Speaking
> frankly I've been thinking about this, but couldn't find a good solution.
> For large XML text insertions maybe it'd better to use something like
> XInclude ot CInclude?
>
> >
> > An example of what I would like to have:
> >
> > <translation lang="en">The <b>first</b> paragraph</translation>
> >
> > giving the translated english result:
> > "The <b>first</b> paragraph"
> >
> > ...later to be serialized into an html file.
> >
> > Howewver, the result is just:
> > "paragraph"
> >
> > I can understand that there is some basic framework constraint I could
be
> > violating, but I don't have the experience to point it out. Could
someone
> do
> > that for me? Anyone with a solution or a work-around?
>
> An ugly workaround is to use separate translation tags for every part,
but,
> sure, it's not a good way:
>
>
<i18n:text>The</i18n:text><b><i18n:text>first</i18n:text></b><i18n:text>para
> graph</i18n:text>.
>
> As I remember, this problem appears because of XML format of dictionaries.
> How would you specify a translation entry like that in the dictionary?
>
> Maybe, we need something like <i18n:xml> tag? But I have no clear idea of
> how to implement it.
>
> >
> > /Gustav
> >
> >
>
> Best regards,
>
> Konstantin Piroumian
> Sr. Software engineer
>
> Protek Flagship LLC
> Phone: + 7 095 795 0520 (add. 1288)
> Fax: + 7 095 795 0525
> E-mail: [EMAIL PROTECTED]
> http://www.protek.com
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.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/faqs.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/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
