Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] variable rtf as querystring in document uri

From: subscriptions <subscriptions@----------->
To:
Date: 12/1/2006 7:30:00 AM
Hi David,

the rtf shown was indeed just an illustration, but can be very big.

Do you know where to get the exslt node-set extension? It is not in the
source-code provided by exslt.org (though it is said on the website).
Others have found this out too.

Greetings,

Rob


On Thu, 2006-11-30 at 10:47 +0000, David Carlisle wrote:
> > So ok..., how do one passes the string through the 'document' command
> > without losing the markup. Do we not have to convert the markup first,
> > before passing it into the document command.
> 
> well it depends, in the example you posted the url string that needed to
> contain tags was just a constant variable in your input and I suggested
> just changing that variable to have markup instead of element nodes.
> 
> If that was just an artifact of the way you simplified it for posting
> and really your $url variable comes from some XML that is constructed
> somewhere then you need to serialise it to a string.
> 
> some systems have extensions to do that, eg saxon8 has
> http://www.saxonica.com/documentation/extensions/functions/serialize.html
> (I can't remember if saxon6 had a similar one)
> or you can apply templates in a mode that does serialisation
> http://www.dpawson.co.uk/xsl/sect4/N10301.html#d13755e49
> But if your xml is in a result tree fragment then you'll need to use
> saxon (or exslt) node-set() extension before you can apply templates to
> it.
> 
> David


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent