Re: encoding problem

2002-10-25 Thread Boris Althaus
hy Bert, we had this problem too. look, if the map:actions section contains following:map:action name="set-encoding" src="org.apache.cocoon.acting.SetCharacterEncodingAction"/ and at the beginning of a pipelinemap:act type="set-encoding"map:parameter name="form-encoding"

Re: encoding problem

2002-10-25 Thread Bert Van Kets
I'm using a build from 14 May 2002. This doesn't have this action yet. I'll check a recent build and try that. Do you mean that I need to add this action at the beginning of EVERY pipeline? Bert At 16:55 25/10/2002 +0200, you wrote: hy Bert, we had this problem too. look, if the map:actions

Re: encoding problem

2002-10-25 Thread Boris Althaus
pe="upd-mitarbeiter"//map:action-set/map:action-sets I don't know if there are other possibilities. Boris - Original Message - From: Bert Van Kets To: [EMAIL PROTECTED] Sent: Friday, October 25, 2002 4:58 PM Subject: Re: encoding problem I'm using a build

Re: Encoding problem with HTML-serializer and URLs

2002-10-14 Thread Alex Romayev
Try this in your sitemap: map:action name=set-character-encoding src=org.apache.cocoon.acting.SetCharacterEncodingAction/ and map:act type=set-character-encoding map:parameter name=form-encoding value=your-encoding/ /map:act --- Stefan Riegel [EMAIL PROTECTED] wrote: Hello,

Re: Encoding problem

2002-09-18 Thread Alex Romayev
Let me be more specific and also simplify the example: Works: xsl:param name=city select='Delhi'/ ... a href=city-detail=$cityxsl:value-of select=$city//a After transformation I get: a href=city-detail=DelhiDelhi/a Does not work: xsl:param name=city select='Äåëè'/ ... a

Re: Encoding problem

2002-09-18 Thread Barbara Post
maybe : a href=city-detail={$city}xsl:value-of select=$city//a try to use Russian-compatible output encoding rather than utf-8 ? - Original Message - From: Alex Romayev [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 12:53 PM Subject: Re: Encoding problem

Re: Encoding problem

2002-09-18 Thread Alex Romayev
- Original Message - From: Alex Romayev [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 12:53 PM Subject: Re: Encoding problem Let me be more specific and also simplify the example: Works: xsl:param name=city select='Delhi'/ ... a href

Re: Encoding problem

2002-09-18 Thread Vadim Gritsenko
Alex Romayev wrote: Let me be more specific and also simplify the example: ... Does not work: xsl:param name=city select='Äåëè'/ Are these funny characters above in UTF-8? Does your XSL has encoding=UTF-8 on the top? ... a href=city-detail=$cityxsl:value-of select=$city//a After

Re: Encoding problem

2002-09-18 Thread Alex Romayev
--- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: Let me be more specific and also simplify the example: ... Does not work: xsl:param name=city select='Äåëè'/ Are these funny characters above in UTF-8? Does your XSL has encoding=UTF-8 on the top? Yes. Also,

Re: Encoding problem

2002-09-18 Thread Vadim Gritsenko
Alex Romayev wrote: --- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: Let me be more specific and also simplify the example: ... Does not work: xsl:param name=city select='Äåëè'/ Are these funny characters above in UTF-8? Does your XSL has

Re: Encoding problem

2002-09-18 Thread Alex Romayev
--- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: --- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: Let me be more specific and also simplify the example: ... Does not work: xsl:param name=city select='Äåëè'/

Re: Encoding problem

2002-09-18 Thread Vadim Gritsenko
Alex Romayev wrote: --- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: --- Vadim Gritsenko [EMAIL PROTECTED] wrote: ... Good point, I may have a problem in another stylesheet (part of the pipeline that responds to the url in question): This parameter is set by the

Re: Encoding problem

2002-09-18 Thread Alex Romayev
--- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: --- Vadim Gritsenko [EMAIL PROTECTED] wrote: Alex Romayev wrote: --- Vadim Gritsenko [EMAIL PROTECTED] wrote: ... Good point, I may have a problem in another stylesheet (part of the pipeline that

Re: encoding problem with xslt

2002-07-12 Thread Joerg Heinicke
Hello Thorsten, there was a bug in Xalan with URL encoding more than a half year ago, but I don't know what's the current status. xsl:template match='c[@color=blue]' xsl:element name=a xsl:attribute name=href frameset.xsp?filename=xsl:value-of

RE: encoding problem with xslt

2002-07-12 Thread Manos Batsis
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] desired output: a href=frameset.xsp?filename=foo.xmlsearchstring=Integrations auml;mter Integrationsauml;mter /a .

Re: encoding problem with xslt

2002-07-12 Thread Joerg Heinicke
Manos Batsis wrote: From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] desired output: a href=frameset.xsp?filename=foo.xmlsearchstring=Integrations auml;mter Integrationsauml;mter /a .

RE: encoding problem with xslt

2002-07-12 Thread Manos Batsis
From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] Still no. Of course you can write this in your XML input, but in the serialized output a valid URL has to be written. And auml; is not valid, the is reserved for concatenating request parameters. My apologies, I should have read the

Re: encoding problem with xslt

2002-07-12 Thread Joerg Heinicke
If anyone has some more ideas on this topic (non-ISO-8859-1 characters within URIs), I would greatly appreciate some more input. Conclusion for me is to avoid such characters in URIs. But this does not get easily into the heads of our customers and users. (e.g. file names) According to the

Re: encoding problem with xslt

2002-07-12 Thread Jens Lorenz
- Original Message - From: Vadim Gritsenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 4:36 PM Subject: RE: encoding problem with xslt From: Jens Lorenz [mailto:[EMAIL PROTECTED]] ... If anyone has some more ideas on this topic (non-ISO-8859-1 characters

Re: encoding problem with xslt

2002-07-12 Thread Jens Lorenz
- Original Message - From: Joerg Heinicke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 4:45 PM Subject: Re: encoding problem with xslt If anyone has some more ideas on this topic (non-ISO-8859-1 characters within URIs), I would greatly appreciate some more

RE: encoding problem with xslt

2002-07-12 Thread Vadim Gritsenko
From: Jens Lorenz [mailto:[EMAIL PROTECTED]] - Original Message - From: Vadim Gritsenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 4:36 PM Subject: RE: encoding problem with xslt From: Jens Lorenz [mailto:[EMAIL PROTECTED]] ... If anyone has

Re: encoding problem with xslt

2002-07-12 Thread Joerg Heinicke
Subject: Re: encoding problem with xslt If anyone has some more ideas on this topic (non-ISO-8859-1 characters within URIs), I would greatly appreciate some more input. Conclusion for me is to avoid such characters in URIs. But this does not get easily into the heads of our customers and users

Re: encoding problem with xslt

2002-07-12 Thread Jens Lorenz
- Original Message - From: Vadim Gritsenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 5:05 PM Subject: RE: encoding problem with xslt snip/ Thanks for you input Vadim. But do not only think of web sites. But also of web applications. Think of a web cms

Re: encoding problem with xslt

2002-07-12 Thread Jens Lorenz
- Original Message - From: Joerg Heinicke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 5:23 PM Subject: Re: encoding problem with xslt Hmm, I didn't test it a long time and didn't find a correlating bug by a short view on Xalan bug list. It was a bug in our