Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 88300 invoked by uid 500); 30 Jan 2003 19:54:49 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 88229 invoked from network); 30 Jan 2003 19:54:49 -0000 Message-ID: <3E398348.9070207@gmx.de> Date: Thu, 30 Jan 2003 20:55:52 +0100 From: Joerg Heinicke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: de-de, de, en, en-us MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: i18n + XSLT transformation References: <000f01c2c527$7e6d8ba0$33f23151@cyrilz4r8zmx1a> <3E397ECC.9020008@gmx.de> <011901c2c898$490a2120$bcd60f50@cyril> In-Reply-To: <011901c2c898$490a2120$bcd60f50@cyril> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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: > > > > > type="xslt-with-parameters"/> > > > > > > > > > > with the declaration of transformer xslt-with-param as bellow: > > src="org.apache.cocoon.transformation.TraxTransformer"> > > true > > > > > > but this does'nt work: > > > > > > > > > > > > > > > > > > > > > > > > > > I thought both syntaxes were valid, aren't they? > > Regards, > > Cyril. > > ----- Original Message ----- > From: "Joerg Heinicke" > To: > 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. >> >>To unsubscribe, e-mail: >>For additional commands, e-mail: >> >> > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: