You have a range of XSLT processor options; goto
http://www.dpawson.co.uk/xsl/sect1/N303.html

I would personally recc. SAXON, to be found at saxon.sourceforge.net

Gl, jim fuller

-----Original Message-----
From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Nicola Martella
Sent: Saturday, November 29, 2003 6:48 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx

Ok Pietschmann, now I've understood.
Under Windows I can use MSXML. Have you some suggestion for a processor
under UNIX/Linux?

Nicola

----- Original Message ----- 
From: "J.Pietschmann" <j3322ptm@xxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, November 28, 2003 8:18 PM
Subject: Re:  File management via XSLT


> Nicola Martella wrote:
> > I'm using <xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">.
> Everybody uses this in the style sheet. The interesting point is: what
> XSLT processor are you using? In case you don't know what an XSLT
> processor is: do you run the transformation in IEx?
>
> Command line processors generally allow you to write the transformation
> result directly to a file. The details are processor specific, check
> the relevant documentation (often "running" or "invoking").
> If you use MSXML from within IEx, get the MSXML command line tools,
> which also allow you to write directly to a file.
>
> If you want to create multiple output files for a transformation, you
> have to use a processor specific extension, as Jarno already told you.
>
> J.Pietschmann
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list