Re: i18n + XSLT transformation

2003-01-30 Thread Joerg Heinicke
Oh, I didn't see that in the original mail. Your elements are wrongly 
nested.  in  is not possible.


  
  

  
  
  


So it should work. Do you really need the request parameters in XSL? 
Because XSLT is always cached with the passed params, you thwart more or 
less effective caching.

Regards,

Joerg

Cyril Vidal wrote:
Thanks for your help Joerg!!

Yes, I found a solution to my problem but I can't really explain it...

This runs well:














with the declaration of transformer xslt-with-param as bellow:



true





but this does'nt work:

























I thought both syntaxes were valid, aren't they?

Regards,

Cyril.

- Original Message -
From: "Joerg Heinicke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 30, 2003 8:36 PM
Subject: Re: i18n + XSLT transformation




Hello Cyril,

found this message just now (I still have nearly 500 unread Cocoon
messages since the weekend). Did you solve the problem? The sitemap
looks ok, maybe the namespace declaration in the XSLT is wrong?

Joerg

Cyril Vidal wrote:


Hi,

Just to go more deeply into Cocoon's comprehension, I've yesterday built


a


little example with the load of two differents stylesheets
(participantsFR.xsl and participantsEN.xsl) depending of the value of a
parameter passed in HTTP Request, and with the help of this


mailing-list,


I've achieved this.

Now, I would like to perform exactly the same task, but by another way:


via


the use of i18n Transformer.

To translate a static xml file, I've no difficult, and the following


except


of sitemap.xmap, (supposed I've created a catalogue directory named
translation with message_en.xml and message_fr.xml) works well:















The following adresses
http://localhost:8080/cocoon/hellococoon/try_it?locale=fr and
http://localhost:8080/cocoon/hellococoon/try_it?locale=en display the
specified translation.



But now, I would like to mix a XSLT transformation with the i18n
Transformation. (I mean, the different

text to be translated  appear now in the XSLT


file


participantsIN.xsl)

To perform this task, I've tried the following code (overlapping the


i18n


transformation inside the XSLT transformation...):





















But when I try by example the following adress:

http://localhost:8080/cocoon/hellococoon/try_it1?locale=en

I receive no error message but nor is the i18n transformation done:

I the HTML result, I have all my text to be
translated elements, without any effective translation.

Waht I have to change in sitemap to fix the problem?

Thanks again for your help,

Cyril.



-
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]>





-
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]>




Re: i18n + XSLT transformation

2003-01-30 Thread Cyril Vidal
Thanks for your help Joerg!!

Yes, I found a solution to my problem but I can't really explain it...

This runs well:














with the declaration of transformer xslt-with-param as bellow:



true





but this does'nt work:

























I thought both syntaxes were valid, aren't they?

Regards,

Cyril.

- Original Message -
From: "Joerg Heinicke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 30, 2003 8:36 PM
Subject: Re: i18n + XSLT transformation


> Hello Cyril,
>
> found this message just now (I still have nearly 500 unread Cocoon
> messages since the weekend). Did you solve the problem? The sitemap
> looks ok, maybe the namespace declaration in the XSLT is wrong?
>
> Joerg
>
> Cyril Vidal wrote:
> > Hi,
> >
> > Just to go more deeply into Cocoon's comprehension, I've yesterday built
a
> > little example with the load of two differents stylesheets
> > (participantsFR.xsl and participantsEN.xsl) depending of the value of a
> > parameter passed in HTTP Request, and with the help of this
mailing-list,
> > I've achieved this.
> >
> > Now, I would like to perform exactly the same task, but by another way:
via
> > the use of i18n Transformer.
> >
> > To translate a static xml file, I've no difficult, and the following
except
> > of sitemap.xmap, (supposed I've created a catalogue directory named
> > translation with message_en.xml and message_fr.xml) works well:
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > The following adresses
> > http://localhost:8080/cocoon/hellococoon/try_it?locale=fr and
> > http://localhost:8080/cocoon/hellococoon/try_it?locale=en display the
> > specified translation.
> >
> >
> >
> > But now, I would like to mix a XSLT transformation with the i18n
> > Transformation. (I mean, the different
> >
> > text to be translated  appear now in the XSLT
file
> > participantsIN.xsl)
> >
> > To perform this task, I've tried the following code (overlapping the
i18n
> > transformation inside the XSLT transformation...):
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > But when I try by example the following adress:
> >
> > http://localhost:8080/cocoon/hellococoon/try_it1?locale=en
> >
> > I receive no error message but nor is the i18n transformation done:
> >
> > I the HTML result, I have all my text to be
> > translated elements, without any effective translation.
> >
> > Waht I have to change in sitemap to fix the problem?
> >
> > Thanks again for your help,
> >
> > Cyril.
>
>
> -
> 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]>




Re: i18n + XSLT transformation

2003-01-30 Thread Joerg Heinicke
Hello Cyril,

found this message just now (I still have nearly 500 unread Cocoon 
messages since the weekend). Did you solve the problem? The sitemap 
looks ok, maybe the namespace declaration in the XSLT is wrong?

Joerg

Cyril Vidal wrote:
Hi,

Just to go more deeply into Cocoon's comprehension, I've yesterday built a
little example with the load of two differents stylesheets
(participantsFR.xsl and participantsEN.xsl) depending of the value of a
parameter passed in HTTP Request, and with the help of this mailing-list,
I've achieved this.

Now, I would like to perform exactly the same task, but by another way: via
the use of i18n Transformer.

To translate a static xml file, I've no difficult, and the following except
of sitemap.xmap, (supposed I've created a catalogue directory named
translation with message_en.xml and message_fr.xml) works well:















The following adresses
http://localhost:8080/cocoon/hellococoon/try_it?locale=fr and
http://localhost:8080/cocoon/hellococoon/try_it?locale=en display the
specified translation.



But now, I would like to mix a XSLT transformation with the i18n
Transformation. (I mean, the different

text to be translated  appear now in the XSLT file
participantsIN.xsl)

To perform this task, I've tried the following code (overlapping the i18n
transformation inside the XSLT transformation...):





















But when I try by example the following adress:

http://localhost:8080/cocoon/hellococoon/try_it1?locale=en

I receive no error message but nor is the i18n transformation done:

I the HTML result, I have all my text to be
translated elements, without any effective translation.

Waht I have to change in sitemap to fix the problem?

Thanks again for your help,

Cyril.



-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>




i18n + XSLT transformation

2003-01-26 Thread Cyril Vidal
Hi,

Just to go more deeply into Cocoon's comprehension, I've yesterday built a
little example with the load of two differents stylesheets
(participantsFR.xsl and participantsEN.xsl) depending of the value of a
parameter passed in HTTP Request, and with the help of this mailing-list,
I've achieved this.

Now, I would like to perform exactly the same task, but by another way: via
the use of i18n Transformer.

To translate a static xml file, I've no difficult, and the following except
of sitemap.xmap, (supposed I've created a catalogue directory named
translation with message_en.xml and message_fr.xml) works well:















The following adresses
http://localhost:8080/cocoon/hellococoon/try_it?locale=fr and
http://localhost:8080/cocoon/hellococoon/try_it?locale=en display the
specified translation.



But now, I would like to mix a XSLT transformation with the i18n
Transformation. (I mean, the different

text to be translated  appear now in the XSLT file
participantsIN.xsl)

To perform this task, I've tried the following code (overlapping the i18n
transformation inside the XSLT transformation...):





















But when I try by example the following adress:

http://localhost:8080/cocoon/hellococoon/try_it1?locale=en

I receive no error message but nor is the i18n transformation done:

I the HTML result, I have all my text to be
translated elements, without any effective translation.

Waht I have to change in sitemap to fix the problem?

Thanks again for your help,

Cyril.


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>