RE: [xsl] Re:

["Chris Bayes" <Chris@xxxxxxxxxxx>]

>>  For instance, if you were using the
>> xalan testXSLT
>> program as your processing engine, you would pipe from one
>> call to another using
>> a command line like the following:
>>
>> testXSLT -in myfile.xml -xsl format.xsl | testXSLT -xsl
>> display.xsl -out
>> myfile.html
>>
>> (I think that syntax should work.)
>
>I think that would be a nice addition to any XSLT engine,
>whether it be a pipeless win32 box

??? win32 isn't pipeless. And from the documentation on
http://msdn.microsoft.com/code/sample.asp?url=/msdn-files/027/001/485/msdnco
mpositedoc.xml

If the ?o option is not specified on the command line, MSXSL will send the
raw output bytes to stdout. This means that the following command will dump
the result of the transformation directly to the console window.
MSXSL books.xml format.xsl
Be aware that if the xsl:output encoding attribute is set to an encoding
that does not match the code page of the console window, strange output may
result.
Stdout can be redirected from the command line using the usual mechanisms.
MSXSL books.xml format.xsl > out.xml
MSXSL books.xml format.xsl | more
A single dash character, '-', can be substituted for either the source or
style sheet argument. This instructs MSXSL to load the source or style sheet
document from stdin rather than from a URL.
MSXSL books.xml format.xsl | MSXSL ? toUTF8.xsl
In this example, a formatted books.xml is piped to an identity
transformation that converts it to UTF 8 for console display. Linking
transformations together like this avoids intermediate file generation.
Errors and timing information are sent to stderr, which can be redirected in
Windows NT. This does not work in Windows 95 and Windows 98.
MSXSL books.xml format.xsl > out.xml 2> err.txt

Ciao Chris


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