Re: How to URL encode?

I have a feeling it is sablotron - you poor, poor man :(  Hey, if it
can't properly transform a document there is the added bonus of being
a fairly fast proccessor -- It would be better if it were fast AND
accurate but you may just want to count your blessings and then take
it up with God if your missing any...

In the mean time the first entry on google returns an interesting
snippet that my explain things quite a bit better and at least
showcase that there is in fact a known problem with lite evidence of a
possible hacked solution.

On 4/22/05, M. David Peterson <m.david.x2x2x@xxxxxxxxx> wrote:
> Brian,
>
> Have you determined what processor you are using?  To do this add the
> following somewhere in your output tree and tell us what value is
> printed:
>
> <xsl:value-of select="system-property('xsl:vendor')"/>
>
> If its a 4.x system you are more than likely using Sablotron and not
> libxslt as you suggested.  Either way, having this knowledge will
> allow you to find out what mechanism the processor uses and then
> determine what workarounds via custom functions have been
> implemented...
>
> On 4/22/05, Brian Dunning <brian@xxxxxxxxxxxxxxxx> wrote:
> > Darn. Oh well, thanks for all your speedy & friendly help. Not sure
> > what I'm going to do yet...   :)  :)
> >
> >
>
> --
> <M:D/>
>
> :: M. David Peterson ::
> XML & XML Transformations, C#, .NET, and Functional Languages Specialist
>


--
<M:D/>

:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist