[Home] [By Thread] [By Date] [Recent Entries]
Bruce,
Since the behavior of xsl:number is dependent only on the context node, all you need to do in general is make sure the context node is correct (along with the instruction's count attribute and all that, of course); where in the stylesheet it appears doesn't matter. In a function, I believe this means passing in your context node as a parameter and changing context to it explicitly before invoking xsl:number. Apart from that (note this is different from a named template, which keeps the context from which it's called), I don't see why it shouldn't work. And it's easy enough to test. As far as a single encapsulated routine (irrespective of how it is implemented), we do that in XSLT 1.0 all the time with named templates, just in the way you're describing -- no problems there. So, a tame goose. Cheers, Wendell At 10:44 AM 5/20/2005, you wrote: On 5/20/05, Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> wrote: ====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
|

Cart



