> 
> Embperl tries to give to libxslt your posted params via fdat, 
> and if these contain non-ascii symbols libxslt fails. 
> If you do not need artifically set up params in your 
> stylesheet (I dont, I want to keep things separated), then 
> you can change line in Embperl/Recipe/EmbperlXSLT.pm 
> 

I have changed things, so parameters are now correctly quoted, so they are
passed as strings, which should avoid such problems.

Of course you can change the recpie (or create your own on and use it) to
avoid parameter passing at all.

If you call your xslt processing via Execute, you can also simply pass an
empty array as xsltparam

The updated version is in the CVS and will be soon released

Gerald


> from:
> 
> push @$ep, {'type' => $xsltproc, stylesheet => [EMAIL PROTECTED], 
> $param -> xsltparam?():(param => \%Embperl::fdat) } ;
> 
> to:
> 
> push @$ep, {'type' => $xsltproc, stylesheet => [EMAIL PROTECTED], 
> $param -> xsltparam } ;
> 
> Neeme Vool
> [EMAIL PROTECTED]
> Codewiser OÜ
> Tel. +372 5151195
> Fax. +372 7409988
> http://www.codewiser.com 
> 
> > -----Original Message-----
> > From: Bjoern Tackmann [mailto:[EMAIL PROTECTED]
> > Sent: 16. august 2004. a. 23:52
> > To: [EMAIL PROTECTED]
> > Subject: Probs with Embperl, LibXSLT
> > 
> > Hi...
> > 
> > there is a strange Problem with Embperl V2 and libxslt 
> which I don't 
> > understand. The Software is Embperl 2.0b10, libxslt
> > 1.0.16 on Linux.
> > 
> > I use EmbperlObject to build the pages, with a user defined recipe, 
> > saying that XSLT will only be used for base.epl -- using 
> the standard 
> > Embperl-recipe for all other files.
> > 
> > For a simple request (GET w/o parameters) this works. But if I POST 
> > some data to that page, I get a "Evaluating user parameter [...] 
> > failed"
> > -- where [...] is the name of the parameter posted -- in my apache 
> > error logs. Embperl sends an error page saying "Error
> > xpath.c:6675:
> > Encoding error:"
> > 
> > Changing the recipe to directly output the xml data gives a 
> plain xml 
> > document that can be "compiled" with xsltproc.
> > 
> > I've spent some time trying to use only standard recipes and stuff 
> > like that, getting the same result all the time.
> > 
> > Thanks in advance for your help and greets from Karlsruhe, Björn 
> > Tackmann
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


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

Reply via email to