I'm using dyn:evaluate
http://www.w3.org/1999/XSL/Transform";
version="1.0"
xmlns:dyn="http://exslt.org/dynamic";
extension-element-prefixes="dyn"
>
//grammar
[...]
The parameters are stylesheet globals so I'm capturing some params from
a URL actually (axkit automatically fills the
At 13:00 Uhr -0500 30.03.2003, S Woodside wrote:
I guess I'll say what everyone was telling me just recently -- can
you provide a slimmer test case? You're using a ton of different
EXSLT extensions, it's hard to see what's going on, and the code is
pretty huge in the function.xsl document.
The d
At 12:55 Uhr -0500 30.03.2003, S Woodside wrote:
I can verify that EXSLT works in 1.6.1 since I'm using it. Why are
you using CVS instead of the released version? (that's as much a
general question as specific to you)
The reason is that I wanted to use xincludes that are going through
some sort
I guess I'll say what everyone was telling me just recently -- can you
provide a slimmer test case? You're using a ton of different EXSLT
extensions, it's hard to see what's going on, and the code is pretty
huge in the function.xsl document.
simon
On Sunday, March 30, 2003, at 07:28 AM, Chris
I can verify that EXSLT works in 1.6.1 since I'm using it. Why are you
using CVS instead of the released version? (that's as much a general
question as specific to you)
simon
On Sunday, March 30, 2003, at 07:28 AM, Christian Jaeger wrote:
For some reason, the current CVS AxKit does *not work
Hello
We are having a hard time trying to get exslt date functions to work,
and have run out of ideas.
Could anyone look at those files and tell us what's wrong?
Look at the Date.xml, Datetext.xsl, and machine*/error.txt files at
the following location:
http://pflanze.mine.nu/~chris/axkit/exsl
