michael
"2>error.log" should work. If not, it's really an operating system
question
rather than a Saxon or XSLT problem, but I guess we can help if you
tell us
exactly what OS environment you are in and what command shell you
are using.
we're working under windows xp. and we're calling a normal .bat file
to start transformation:
[process.bat]
set errorfilename=C:\errors\%date:~-4%%date:~-7,2%%date:~-10,2%.log
set saxdir=C:\Programme\saxonb8
set filedir=C:\XMLBatchProcessor\input
java -jar %saxdir%\saxon8.jar -o %3 %3 first.xsl >> %errorfilename%
..
.. (calling further xslts)
..
..
- %3 represents full path and filename of the xml file to be transformed
- 'errorfilename' will be used as '20060921.log'
- '2>> % errorfilename%' was writing saxon error messages, but did
*not* write xsl:message messages
- '>> % errorfilename%' produces no output
- we're not able to implement a MessageEmitter and only working
on .bat level
appreciating your help,
hoping my information is enough detailled
frank
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--