Subject: Re: lists as parameters From: "Dan Machak" <machak@xxxxxxxxxxxx> Date: Fri, 6 Aug 1999 10:29:21 -0700 |
On Aug 6, 12:18pm, Jon Smirl wrote: > ... > One idea I had is writing an extension function that would take a comma > separated list and return it as a node list for use in a for-each, but it > doesn't look like I can return a node-list from an extension function. I tried the same thing. Another approach I've considered is to handle it during the XML parsing stage. I think it might be possible to provide a method to the XML parser that will handle the list and return it as a set of elements. This would involve customizing the SAX parser being used (by extending the DocumentHandler being used?). I haven't had any experience with this yet. However, I would like to see direct support for this conversion. Would there be a problem with providing a function node-set parse(string) in XSLT? This would take an XML-encoded string and return a node-set. This would allow extension functions to process arbitrary text and return a set of nodes encoded as a string. Dan > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list >-- End of excerpt from Jon Smirl -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> <> Dan Machak <> machak@xxxxxxxxxxxx <> <> MS T27A-1 <> 650-604-2388 (VOICE) <> <> NASA Ames Research Center <> 650-604-3957 (FAX) <> <> Moffett Field, CA 94035-1000 <> <> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: lists as parameters, Jon Smirl | Thread | Re: lists as parameters, Oren Ben-Kiki |
spaces with SAXON, Zsolt Czinkos | Date | Re: Pb with identity transform in X, Dan Machak |
Month |