[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: example for xsl:output saxon:next-in-chain
Hi Ana,
Like Mike, I couldn't see any way this was broken. If it were me, I'd start by checking the really bone-headed stuff: Are you actually using Saxon? Are you actually calling the "wrapper" stylesheet, not the "first.xsl" stylesheet it imports (which doesn't use the next-in-chain feature)? This is the kind of thing Mike means by needing to know how you are invoking the transformation. Of course it's probably not so simple as what I've suggested -- but I find I save myself trouble (and the temporary loss of my self-respect) if I check this level of things first, rather than proceeding to troubleshoot more deeply on the assumption that it could never be anything so dumb. (It could.) It's sort of like checking to see whether the machine is plugged in before calling tech support when it won't power up. The only people who don't need to do this are the ones who are in the habit of doing it anyway. If everything is wired correctly, Mike is correct, it's Saxon-specific. Cheers, Wendell At 09:13 AM 2/10/2005, Mike wrote: The best place for Saxon-specific questions is the saxon-help list or forum at sourceforge.net. ====================================================================== 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 ======================================================================
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|